Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0
-
Fix Version/s: 10.2.9
-
Component/s: Storage Engine - InnoDB
-
Labels:
Description
The test encryption.innodb-spatial-index creates a table with ENCRYPTED=YES, and then expects an ADD SPATIAL INDEX, ALGORITHM=COPY operation to fail. However, an operation with FORCE, ALGORITHM=COPY is just fine (in both 10.1 and 10.2):
--source include/have_innodb.inc
|
--source include/have_file_key_management_plugin.inc
|
|
CREATE TABLE t1 (pk INT PRIMARY KEY AUTO_INCREMENT, |
c VARCHAR(256), coordinate POINT NOT NULL) ENCRYPTED=YES ENGINE=INNODB; |
ALTER TABLE t1 FORCE, ALGORITHM=COPY; |
ALTER TABLE t1 FORCE, ALGORITHM=INPLACE; |
DROP TABLE t1; |
In my opinion, ALTER TABLE...ALGORITHM=COPY must always succeed, and it must always preserve those table attributes that were not specified in the ALTER.
Attachments
Issue Links
- is caused by
-
MDEV-11974 Disable encryption of spatial indexes in MariaDB 10.2
-
- Closed
-
-
MDEV-13847 Allow ALTER TABLE…ADD SPATIAL INDEX…ALGORITHM=INPLACE
-
- Closed
-