[MDEV-19989] Implement upgrade checker utility Created: 2019-07-08  Updated: 2023-06-09

Status: Open
Project: MariaDB Server
Component/s: Scripts & Clients, Server
Fix Version/s: None

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Ralf Gebhardt
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-9394 Automatic dictionary upgrade on serve... Open

 Description   

The MySQL Shell utility has a contains am "Upgrade Checker Utility" starting with MySQL 8.0.13:

7.1 Upgrade Checker Utility
The util.checkForServerUpgrade() function is an upgrade checker utility that enables you to verify whether MySQL server instances are ready for upgrade. From MySQL Shell 8.0.13, you can select a target MySQL Server release to which you plan to upgrade, ranging from the first MySQL Server 8.0 General Availability (GA) release (8.0.11), up to the MySQL Server release number that matches the current MySQL Shell release number. The upgrade checker utility carries out the automated checks that are relevant for the specified target release, and advises you of further relevant checks that you should make manually.

You can use the upgrade checker utility to check MySQL 5.7 server instances for compatibility errors and issues for upgrading. From MySQL Shell 8.0.13, you can also use it to check MySQL 8.0 server instances at another GA status release within the MySQL 8.0 release series. If you invoke checkForServerUpgrade() without specifying a MySQL Server instance, the instance currently connected to the global session is checked. To see the currently connected instance, issue the \status command.

https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-upgrade.html

Some users would like MariaDB to also have an upgrade checker utility that could determine whether an existing MariaDB or MySQL server is compatible with an upgrade to a specific MariaDB version.



 Comments   
Comment by Sergei Golubchik [ 2019-07-09 ]

We don't have mysqlsh, but this is something that could be done as mysql_uprade --dry-run, albeit less verbosely.

with the current implementation, mysql_uprade --dry-run might be quite difficult to add, but from the user point of view it'd be a very reasonable and easy feature

Comment by Geoff Montee (Inactive) [ 2019-07-09 ]

mysql_upgrade --dry-run sounds pretty intuitive.

Are there plans to get rid of mysql_upgrade in the future (i.e. such as by implementing MDEV-9394)?

Comment by Daniel Black [ 2022-05-05 ]

MDEV-27279 already implemented this, though MDEV-27636 is outstanding.

Generated at Thu Feb 08 08:55:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.