Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.5.3
-
None
Description
This feature should work for both the "force drop" introduced by MDEV-11412 and for multi-table drop. Currently it throws an error when doing a multi table drop statement on ANY engine if Columnstore is installed, but the table being dropped does not exist.
This is very easy to reproduce. The following is an example of loading the sample "Employees" dataset from datacharmer. These are InnoDB tables and yet we still get a Columnstore error:
[root@mcs1 vagrant]# git clone https://github.com/datacharmer/test_db.git |
Cloning into 'test_db'... |
remote: Enumerating objects: 105, done. |
remote: Total 105 (delta 0), reused 0 (delta 0), pack-reused 105 |
Receiving objects: 100% (105/105), 74.27 MiB | 16.35 MiB/s, done. |
Resolving deltas: 100% (54/54), done. |
|
|
[root@mcs1 vagrant]# cd test_db/ |
|
|
[root@mcs1 test_db]# mysql < employees.sql |
INFO
|
CREATING DATABASE STRUCTURE
|
ERROR 1178 (42000) at line 31: The storage engine for the table doesn't support The syntax or the data type(s) is not supported by Columnstore. Please check the Columnstore syntax guide for supported sy |
ntax or data types.
|
This is the statement that throws the error:
DROP TABLE IF EXISTS dept_emp,
|
dept_manager,
|
titles,
|
salaries,
|
employees,
|
departments;
|
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
MDEV-11412 Ensure that table is truly dropped when using DROP TABLE
-
- Closed
-