Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-13851

Always check table options in ALTER TABLE…ALGORITHM=INPLACE

    XMLWordPrintable

    Details

      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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11974 Disable encryption of spatial indexes in MariaDB 10.2

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13847 Allow ALTER TABLE…ADD SPATIAL INDEX…ALGORITHM=INPLACE

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.