This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

Will MariaDB 10.1.X pick up MySQL 5.7.7 system variable changes for innodb?

Will MariaDB 10.1.X pick up MySQL 5.7.7 system variable changes for innodb?

http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_large_prefix • innodb_large_prefix is enabled by default in MySQL 5.7.7. This change coincides with the default value change for innodb_file_format, which is set to Barracuda by default in MySQL 5.7.7. Together, these default value changes allow larger column prefix indexes to be created when using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED. If either option is set to a non-default value, column prefixes are silently truncated to 768 bytes. innodb_large_prefix is deprecated in MySQL 5.7.7, and will be removed in a future release. innodb_large_prefix was introduced in MySQL 5.5 to allow users to create tables compatible with the InnoDB Plugin in MySQL 5.1, which has reached the end of its product lifecycle.

Answer

We will have all (or almost all) InnoDB changes from MySQL 5.7 eventually. But I cannot say whether it will be in 10.1 or 10.2 — 5.7 is still having "development milestone releases", and if it won't get production-ready before 10.1, we won't be able to use InnoDB-5.7 in 10.1.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.