Maintenance Release Changelog

Disabled semi-join operator reduction optimization.

Fixed an issue where the query optimizer could choose incorrectly between using the HashGroupBy or the StreamingGroupBy operators.

Added more information about blob files that need to be downloaded from unlimited storage to the blob cache when running PROFILE.

Fixed rare issue with sync durability and unlimited storage that could cause log file corruption in the blob storage.

Fixed an issue with optimizing queries containing no-operation predicates such as 1=1.

Improved the performance of a left join of a reference table with a sharded table by pushing the reference table clauses to the leaves. The engine variable disable_reference_table_leftjoin_where_pushdown must be set to "OFF" to enable this operation.

Now allowing child aggregator root users to be dropped even if the sync_permissionengine variable is enabled.

Removed the restrictions on the names of JWT users. Customers may now create users with names that look like UUIDs and emails.

Fixed a bug with error handling that produced spam messages.

Backups taken from the 8.1.3 release (and subsequent 8.1 releases) are no longer restorable into the previous 8.1 releases (8.1.1 and 8.1.2).

Removed the EXECUTE permission requirements for MongoDB API internal UDFs.

Changed the system information built-ins to use the utf8_general_ci collation for the collation_server value.