As of Clustrix 9, the global variable version has changed to be editable and is now used for MySQL compatibility only. A new global variable, clustrix_version is used to display the current version of the ClustrixDB software. The version global variable will no longer be updated automatically on upgrade. If you were using an older version of ClustrixDB, after upgrading to Clustrix 9, update version global to remove the Clustrix version and set it to the desired MySQL version.
sql> set global version = ‘5.0.45-clustrix’;
Changing this value may cause your application’s behavior to change.
These are the global variables related to version.
Clustrix software version
The reported MySQL server version
|format_version||A version string indicating the version of the software when the cluster was initial created.||<auto populated>|
Caveats to Version Compatibility
Replication to MySQL
Clustrix emulates MySQL replication. Setting the value of version on a Clustrix master can affect the expected results on a MySQL slave.
If you set the version value on Clustrix to a MySQL 5.6 version (e.g. 5.6.38), RBR replication to MySQL 5.5 will succeed, but replication to MySQL 5.6 and MySQL 5.7 is not supported. To replicate to MySQL 5.6 or MySQL 5.7, the version on the Clustrix master should be set to 5.0.45-clustrix.
Changing the MySQL value contained in version can have an impact on JDBC behavior, as JDBC will read the version and attempt to use features accordingly. ClustrixDB does not support the tx_read_only variable, which is used by JDBC when some specific MySQL values are set in version. The following chart outlines compatibility of Clustrix with different values for version and versions of JDBC:
|5.1.32||Not Supported||Not Supported||Not Supported|
|5.1.36||Not Supported||Not Supported||Not Supported|