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

ER_UNSUPPORTED_EXTENSION upon using HASH keys with InnoDB

    XMLWordPrintable

Details

    Description

      Not related directly to vectors, but caused by changes in the vector branch.

      --source include/have_innodb.inc
      		 
       
      		 
      CREATE TABLE t (a INT, KEY(a) USING HASH) ENGINE=InnoDB;
      		 
      UPDATE t SET a = 1 WHERE a > 1;
      		 
       
      		 
      # Cleanup
      		 
      DROP TABLE t;

      bb-11.6-MDEV-32887-vector 77be73c489fb7c21ca58e78cef10e0c166f293d8

      		 
      query 'UPDATE t SET a = 1 WHERE a > 1' failed: ER_UNSUPPORTED_EXTENSION (1112): Table 't' uses an extension that doesn't exist in this MariaDB version

      The failure started happening after this commit:

      commit 8d2bd8dd714e94a2df7ab6566d1f4c465a79ef9a
      		 
      Author: Sergei Golubchik
      		 
      Date:   Sun Jan 14 11:43:43 2024 +0100
      		 
       
          cleanup: key algorithm vs key flags

      Attachments

        Issue Links

          is caused by

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34939 vector search in 11.7

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35077 Assertion failure in myrocks::ha_rocksdb::position_to_correct_key upon using unique hash key

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

          Activity

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.