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

DATA/INDEX DIRECTORY handling is inconsistent

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.5, 10.6, 10.11, 11.4, 11.7(EOL), 11.8
    • 11.8.2
    • Plugins
    • None

    Description

      DATA/INDEX DIRECTORY handling is inconsistent between different engines.

      E.g. CSV ignores them. Archive throws a warning that INDEX DIRECTORY is not supported. InnoDB throws an error that INDEX DIRECTORY is not supported.

      We want all engines to behave consistently. Either they should ignore unsupported DIRECTORY options, or ignore with a warning, or fail with an error

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35152 DATA/INDEX DIRECTORY options are ignored for vector index

          • Major - Major loss of function.
          • Closed

          Activity

            serg Sergei Golubchik added a comment - - edited

            Implemented behavior:

            • the fix covers archive/csv/innodb/rocksdb
            • all these engines issue a note for unsupported options, like "DATA DIRECTORY option ignored"
            • engines only issue a note "INDEX DIRECTORY option ignored" if the engine stores indexes somewhere else, not in the INDEX DIRECTORY. That is:
              • there's no such note if the table has no indexes
              • there's no such note if indexes are actually stored in the INDEX DIRECTORY. This is the case with InnoDB when DATA DIRECTORY is the same as INDEX DIRECTORY
            serg Sergei Golubchik added a comment - - edited Implemented behavior: the fix covers archive/csv/innodb/rocksdb all these engines issue a note for unsupported options, like "DATA DIRECTORY option ignored" engines only issue a note "INDEX DIRECTORY option ignored" if the engine stores indexes somewhere else, not in the INDEX DIRECTORY. That is: there's no such note if the table has no indexes there's no such note if indexes are actually stored in the INDEX DIRECTORY. This is the case with InnoDB when DATA DIRECTORY is the same as INDEX DIRECTORY

            People

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