Release Notes for MariaDB MaxScale 6.3.1

When Avrorouter replicates binary log events that reference sequencessequences, MaxScale can crash. (MXS-4120)

When the Kafka CDC router (kafkacdc), is being used with a match or exclude statement a crash occurs with an error like: (MXS-4099)

alert  : MaxScale 6.3.0 received fatal signal 11.
alert  : Statement currently being classified: none/unknown

Using a mix of MariaDB 10.2.7 and MariaDB 10.6 back-ends can cause MaxScale to crash. (MXS-4101)

If the value of the query_classifier_cache_size parameter is set high, executing maxctrl show qc_cache can cause MaxCtrl to run out of memory. (MXS-4121)

When Schema Router (schemarouter) is used, the sys schema is not automatically ignored for duplicate checks. (MXS-4110)

• In earlier releases, the ignore_tables_regex parameter would have to be used to configure Schema Router (schemarouter) to ignore the sys schema when used with MariaDB Enterprise Server 10.6.

• Starting with this release, Schema Router (schemarouter) will automatically ignore the sys schema for duplicate checks.

With the MaxScale REST API, the /user/inet endpoint fails schema validation when used with the newest schema for the JSON API specification. (MXS-4109)

Executing the SHOW SLAVE STATUS statement via the MaxScale Binlog router (binlogrouter) does not show SSL information. (MXS-4096)

Duplicate table errors for tables where the table names are in different cases, for example table.t1 and table.T1 (MXS-4092)

• Starting with this release, Schema router (schemarouter) compares table and database names case-sensitively. This means that the tables test.t1 and test.T1 are seen as different tables.

• Prior to this release, Schema router (schemarouter) compares table and database names case-insensitively. This can cause duplicate tables to be found if the server supports case-sensitive table names.

The MaxScale REST API is inaccessible after deleting the last REST API user. (MXS-4086)

• Starting with this release, it is no longer possible to delete all the REST API users. There will always be one user, "the last user", remaining.

• Prior to this release, it is possible to delete every user of the REST API which would leave the REST API inaccessible.

When multiple servers are selected as Master with Read Connection Router (readconnroute), the rank parameter is ignored for all servers except the last one. (MXS-4132)

• In earlier releases, this could impact query routing in some configurations. For example, let's say that two servers are selected as Master: the first has rank=primary, and the second has rank=secondary. When router_options=master is set, Read Connection Router (readconnroute) chooses the second server, because the rank of the first server is ignored.

When a service uses the targets parameter to route queries to a second service, the second service is not shown as a target in the output of maxctrl list services. (MXS-4127)

When the Read/Write Split router (readwritesplit) is configured with use_sql_variables_in=master, the query is routed normally but the following error is logged: (MXS-4111)

error  : (1) [readwritesplit] (RW-Split-Router); Can't route COM_QUERY 'SELECT CASE data WHEN 'hello' THEN @var:=2 ELSE @var:=1 END'. SELECT with session data modification is not supported with `use_sql_variables_in=all`.

Avro router (avrorouter) with CDC to Kafka can fail for some tables. (MXS-4095)

MaxScale deployments using Redis and the Spyder IDE tool fail with the error (OperationalError: (2013, 'Lost connection to MySQL server during query')) (MXS-4091)

In MaxGUI, the parameter's tooltip shows unnecessary attributes. (MXS-4088)