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

enforce_storage_engine option

        Details

        • Type: Task
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Fix Version/s: 10.1.4
        • Component/s: OTHER
        • Labels:
          None

          Description

          We should support enforce_storage_engine, like Percona Server 5.5/5.6 has. Description: http://www.percona.com/doc/percona-server/5.6/management/enforce_engine.html

          Use case: To improve management – eg. enforce_storage_engine=InnoDB – this ensures that people don't create MyISAM tables by accident.

          Customer requests: There have been no customer requests for this yet from MariaDB Corporation.

          1. It is however likely used in HPCloud, DBaaS – see: https://github.com/saurabhsurana/trove-installer/blob/f7cf7824fb7536b16da073ba7fdb0e717da26fb1/saltstack/states/trove/taskmanager/mysql.config.template

          2. We have had a migration from MariaDB 10 to Percona Server 5.6 at a bank in Germany performed by FromDual for this very reason – http://www.fromdual.ch/de/node/1074

            Gliffy Diagrams

              Attachments

                Issue Links

                is duplicated by

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8357 Ability to disable creation of MyISAM tables

                • Major - Major loss of function.
                • Closed
                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8578 Wrong error code/message with enforce_storage_engine and NO_ENGINE_SUBSTITUTION

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Confirmed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8577 With enforce-storage-engine mysql_upgrade corrupts the schema: ALTER TABLE should either bypass enforce-storage-engine, or mysql_upgrade should refuse to run

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

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8219 enforce_storage_engine cannot be set globally

                • Major - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-8576 Bootstrap should ignore --enforce-storage-engine option

                • Major - Major loss of function.
                • Closed

                  Activity

                  Ascending order - Click to sort in descending order
                  5 older comments
                  Hide
                  Permalink
                  jplindst Jan Lindström added a comment -

                  http://lists.askmonty.org/pipermail/commits/2015-March/007550.html

                  Show
                  jplindst Jan Lindström added a comment - http://lists.askmonty.org/pipermail/commits/2015-March/007550.html
                  Hide
                  Permalink
                  jplindst Jan Lindström added a comment -

                  commit 8249dcaaebf8cd1944bd4ab7ccaa8b199e76d6f9
                  Author: Jan Lindström <jan.lindstrom@mariadb.com>
                  Date: Tue Mar 10 08:28:51 2015 +0200

                  MDEV-6858: enforce_storage_engine option

                  Merge from Percona Server enforced use of a specific storage engine
                  authored by Stewart Smith.

                  Modified to be session variable and modifiable only by SUPER. Use
                  similar implementation as default_storage_engine.

                  Show
                  jplindst Jan Lindström added a comment - commit 8249dcaaebf8cd1944bd4ab7ccaa8b199e76d6f9 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Tue Mar 10 08:28:51 2015 +0200 MDEV-6858 : enforce_storage_engine option Merge from Percona Server enforced use of a specific storage engine authored by Stewart Smith. Modified to be session variable and modifiable only by SUPER. Use similar implementation as default_storage_engine.
                  Hide
                  Permalink
                  otto Otto Kekäläinen added a comment -

                  Is this backported to 10.0.x or really only in 10.1.4 as the "Fix version" says?

                  Show
                  otto Otto Kekäläinen added a comment - Is this backported to 10.0.x or really only in 10.1.4 as the "Fix version" says?
                  Hide
                  Permalink
                  otto Otto Kekäläinen added a comment -

                  At least MariaDB 10.0.20 complains ```[ERROR] /usr/sbin/mysqld: unknown variable 'enforce_storage_engine=InnoDB'``` so it is not backported to 10.0 series.

                  Show
                  otto Otto Kekäläinen added a comment - At least MariaDB 10.0.20 complains ``` [ERROR] /usr/sbin/mysqld: unknown variable 'enforce_storage_engine=InnoDB'``` so it is not backported to 10.0 series.
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  As the Fix version/s field states, it's 10.1 only. I don't know if such a thing can be backported into a long-after-GA version.

                  Show
                  elenst Elena Stepanova added a comment - As the Fix version/s field states, it's 10.1 only. I don't know if such a thing can be backported into a long-after-GA version.

                    People

                    • Assignee:
                      jplindst Jan Lindström
                      Reporter:
                      colin Colin Charles
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      8 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Time Tracking

                        Estimated:
                        Original Estimate - Not Specified
                        Not Specified
                        Remaining:
                        Remaining Estimate - 0 minutes
                        0m
                        Logged:
                        Time Spent - 2 hours, 15 minutes
                        2h 15m