Xpand provides general compatibility with MySQL and MariaDB functionality, but does not guarantee compatibility with any particular version. For the purposes of third party tools, you can configure Xpand to display a specific version.
The value for the version variable will is a concatenation of mysql_version and clustrix_version. The value for mysql_version should be set according to your compatibility needs and the clustrix_version global variable is updated automatically on database upgrade.
sql> select @@version;
Changing the value of mysql_version may cause your application’s behavior to change.
These are the global variables related to version.
Xpand 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>|
|version||The reported server version||<auto populated>|
Caveats to Version Compatibility
Replication from Xpand (Master) to MySQL (Slave)
Xpand can replicate to the following versions of MySQL with the using the specified values set for mysql_version on the Xpand master. See Using Xpand as a Replication Master for instructions on configuration.
|MySQL version (slave)|
|Xpand mysql_version (master)||5.0.*||5.5||5.6||5.7|
Replication from Xpand to Xpand is not affected by the value for mysql_version.
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. Xpand 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 Xpand 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|