MySQL :: MySQL 26.7 Release Notes :: Changes in MySQL 26.7.0 (Early Access Release)

The server could close unexpectedly if audit_log_encryption_password_get(keyring ID) was called. (Bug #33296125)
The following new Audit Log status variables are introduced in this version:
- audit_log_file_count (Audit plugin)
- audit_log.file_count (Audit component)
This variable reports the number of audit log files generated by the Audit Log plugin or component when audit_log_format=JSON. The value is incremented for automatic rotations and decremented for pruning actions. (WL #17292)

The command-service default DOM consumer stored SQL NULL fields as literal NULL string and recomputed field lengths with strlen() from the buffered row. This made SQL NULL indistinguishable from a real "NULL" value and truncated binary values at embedded NUL bytes. (Bug #39405458)
In previous releases, command-service consumers did not have a public mysql_command_options API to set or read extra client flags on a command-service MYSQL connection.

The new command-services option, MYSQL_COMMAND_CLIENT_FLAGS passes client flags to mysql_real_connect().

Custom consumers can continue to override command capabilities with MYSQL_TEXT_CONSUMER_CLIENT_CAPABILITIES. The callback delegate remains unaware of MYSQL_COMMAND_CLIENT_FLAGS. (Bug #39349732)

Data dictionary validation now checks invalid SET definitions with no elements in addition to ENUM definitions.

Our thanks to Yongfei Ji for the contribution. (Bug #36357937)

The following replication system variables are deprecated in and scheduled for removal in a later release:
- group_replication_communication_stack
- group_replication_ip_allowlist
(WL #17300)

InnoDB: Fixed an issue relating to Clone validation. (Bug #39252970)
InnoDB: Fixed an issue relating to table maintenance and clean-up. (Bug #39091376)
InnoDB: Fixed an issue relating to unique indexes. (Bug #38501299)
MySQL Clone plugin supports the updated CalVer model.
- Cloning is allowed when the version strings match.
- Cloning is allowed across patch versions of a given version.
- Cloning is allowed from Donor in one LTS to Recipient in next LTS.
- Cloning is not allowed from donor in one LTS to recipient in an older LTS.
- Cloning is not allowed from donor in one LTS to recipient in a later LTS.
- Cloning is not allowed if either donor or recipient is not LTS and the Major and/or Minor versions mismatch.
(WL #17317)
InnoDB undo tablespace creation and truncation no longer rely on a local undo truncate log files. Undo truncation progress information is now stored in the Undo Tablespace header.

As of this release, undo truncation logs are no longer generated.

Note

For backward compatibility, existing truncate log files are still supported, but no new truncate logs logs are created.

(WL #16989, WL #17187)

Fixed several issues relating to validations in Group Replication. (Bug #39234600, Bug #38673268, Bug #38673285, Bug #38712932, Bug #39253416, Bug #39282368)
As of this release, the default value of group_replication_communication_stack is changed from XCOM to MYSQL. (WL #15709)

MySQL Thread Pool plugin, formerly only available in MySQL Enterprise Edition, is now available in MySQL Community Edition 26.7.0. (WL #17296)

Important Change: MySQL Server now uses calendar-based versioning for releases after the 9.7 LTS series. Version values use Year.Month.Patch (YY.M.P) format. MySQL 26.7.0 is the first such calendar-version release.

The following are added to the mysql_version.h to identify the previous LTS version:
- MYSQL_PREVIOUS_LTS_VERSION: The previous LTS version number. For example, "9.7.0" is the previous LTS version for MySQL 26.7.0.
- MYSQL_PREVIOUS_LTS_VERSION_ID: The identifier of the previous LTS version. For example, "9.7.0" is represented as 90700.
The versioning lineage defined in mysql_version.h enables clear upgrade and downgrade paths. (WL #17310)

Fixed an issue in Spatial Data handling. (Bug #39489004)
Fixed several issues in the Clone plugin. (Bug #39252316, Bug #39245805, Bug #39245844, Bug #39253040, Bug #39253103)