In ClustrixDB 9.1, the value for version is a concatenation of mysql_version and clustrix_version. The value for mysql_version should be set according to your compatibility needs. The value for clustrix_version is updated automatically on upgrade.
sql> select @@version; +---------------------+ | @@version | +---------------------+ | 5.0.45-clustrix-9.1 | +---------------------+ 1 row in set (0.00 sec)
Changing the value of mysql_version may cause your application’s behavior to change. Clustrix recommends testing non-default values of mysql_version in a development environment to ensure compatibility.
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>|
Concatenation of mysql_version and clustrix_version.
Caveats to Version Compatibility
Replication from ClustrixDB (Master) to MySQL (Slave)
ClustrixDB can replicate to the following versions of MySQL with the using the specified values set for mysql_version on the ClustrixDB master.
|MySQL version (slave)|
|ClustrixDB mysql_version (master)||5.0.*||5.5||5.6||5.7|
Replication from ClustrixDB to ClustrixDB is not affected by the value for mysql_version. See Using ClustrixDB as a Replication Master for instructions on configuration.
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|