Changes in MySQL Shell 8.4.4 (2025-01-21, LTS Release)

• AdminAPI Bugs Fixed

• Utilities Added or Changed Functionality

• Utilities Bugs Fixed

• Functionality Added or Changed

• Bugs Fixed

AdminAPI Bugs Fixed

• replicationLag of ReplicaSet.status() returned null if replication was idle.

  As of this release, the following changes were made:

  • replicationLag is set to null if the replication connection, or SQL thread, is not running.

  • replicationLag is set to applier_queue_applied when the last queued transaction matches the last applied transaction, or the applying transaction count is 0 (zero).

  (Bug #35914505)

• It was not possible to remove a member from a ReplicaSet using ReplicaSet.removeInstance() with the force option enabled, if the member was in an ERROR state. (Bug #35282392)

• The ReplicaSet metadata schema table, INSTANCES, was not populated properly when upgrading the metadata schema to version 2.2.0. As a result, MySQL Router did not recognize the topology and rejected connections to it. (Bug #116231, Bug #37101286)

Utilities Added or Changed Functionality

• The schema MYSQL_AUTOPILOT is excluded by dump and load operations with ocimds:true. (Bug #37278169)

• As of this release, the upgrade checker utility writes all compatibility issues and fixes to the log file, instead of only writing to the console. (Bug #37154456)

Utilities Bugs Fixed

• If convertBsonTypes was enabled, the JSON import utility failed when importing negative BSON values.

  An error similar to the following was returned:

  Press CTRL+C to copy
   
          ValueError: Unexpected data, expected to find an integer string processing extended JSON for $numberInt at offset 25

  (Bug #37243264)

• Amazon RDS made the following changes in 8.0.36:

  • It is no longer possible to grant BACKUP_ADMIN.

  • It is no longer possible to lock MySQL system tables.

  As a result, consistent dumps from Amazon RDS are not possible.

  As of this release, if locking the MySQL system tables fails with an Access Denied error, a warning is printed and the dump continues.

  Additionally, for non-Amazon RDS instances, if the user has the BACKUP_ADMIN privilege and LOCK INSTANCE FOR BACKUP succeeds, the MySQL system tables are not locked. (Bug #37226153)

• Under certain circumstances, such as a large amount of data chunking, the maxRate dump option did not properly limit the throughput due to a gap between the start of the dump and the start of the data dump. As of this release, maxRate is used only when data is being dumped. (Bug #37216767)

• MySQL Shell could hang when running a dump with consistent: true under an account which lacked privileges to execute FLUSH TABLES WITH READ LOCK.

  As of this release, query events are checked only if they contain data, and GRANT and REVOKE statements are flagged as unsafe. (Bug #37158908)

Functionality Added or Changed

• As of this release, the Google V8 JavaScript engine is replaced by Oracle GraalVM. (Bug #34370637)

Bugs Fixed

• In MySQL Shell 8.0.40, RPM installation failed on Oracle Linux 8 due to a dependency on Python 3.9. As of this release, MySQL Shell bundles Python 3.13. (Bug #37479400)

• Under certain circumstances, a Ctrl+c key combination could lead to a deadlock. (Bug #35998250)