Details

    Description

      Many InnoDB system variables have changes described as "deprecated and ignored". A correct description would be parsed but ignored.

      The usage of "deprecated" within MySQL and within IT in general is for features that are still supported but will likely be removed in a future release – deprecation is step 1, removal is step 2. But MariaDB combines these into one step, and even worse – parses and ignores them to make upgrades easier but leading to my.cnf settings that don't do what you expect them to do.

      So my request is to stop using "deprecated and ignored". You are welcome to use "parsed but ignored" although I am also not a fan of that because MySQL already has a way to safely do "parse but ignored" via the "loose_" prefix

      Attachments

        Activity

          Some server features (including some InnoDB system variables) are truly "deprecated and ignored". Meaning, they are still supported, you can see then in SHOW VARIABLES and INFORMATION SCHEMA, you can use them in SET and SELECT. But changing them has no effect (= ignored), and eventually they will be removed (=deprecated).

          But you're also right there are variables which were already removed and are only recognized as command line options to not break cnf files (which I think is a misfeature, they should've been completely removed) — they should not be listed as "deprecated" anymore.

          serg Sergei Golubchik added a comment - Some server features (including some InnoDB system variables) are truly "deprecated and ignored". Meaning, they are still supported, you can see then in SHOW VARIABLES and INFORMATION SCHEMA, you can use them in SET and SELECT. But changing them has no effect (= ignored), and eventually they will be removed (=deprecated). But you're also right there are variables which were already removed and are only recognized as command line options to not break cnf files (which I think is a misfeature, they should've been completely removed) — they should not be listed as "deprecated" anymore.

          If they parsed but ignored, then they aren't still supported.

          mdcallag Mark Callaghan added a comment - If they parsed but ignored, then they aren't still supported.

          I would settle for a my.cnf option that disables this behavior.

          mdcallag Mark Callaghan added a comment - I would settle for a my.cnf option that disables this behavior.

          I believe that mdcallag could mean that there should be a way to disable all MARIADB_REMOVED_OPTION(), to get errors for using parameters that have been removed, like MySQL and MariaDB used to work until rather recently. Configuration files that are compatible with both old and new releases could always be written by using the loose_ prefix.

          marko Marko Mäkelä added a comment - I believe that mdcallag could mean that there should be a way to disable all MARIADB_REMOVED_OPTION() , to get errors for using parameters that have been removed, like MySQL and MariaDB used to work until rather recently. Configuration files that are compatible with both old and new releases could always be written by using the loose_ prefix.

          People

            greenman Ian Gilfillan
            mdcallag Mark Callaghan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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