[MXS-180] MariaDB10 binlog router compatibilty Created: 2015-06-03  Updated: 2015-07-16  Resolved: 2015-07-16

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 1.1.0
Fix Version/s: 1.2.0

Type: Bug Priority: Major
Reporter: Massimiliano Pinto (Inactive) Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
includes MXS-182 SHOW SLAVE STATUS and maxadmin "show ... Closed

 Description   

In the binlog router machine for MariaDB10 compatibility SELECT VERSION and SELECT @@version_comment limit 1 were missing: those queries are now sent to master and the reply cached.

https://github.com/mariadb-corporation/MaxScale/tree/binlog_router_mariadb10

Now binlog router could be used with MariaDB 10 with this steps in maxscale.cnf:

[Binlog_Service]
type=service
router=binlogrouter
servers=master
version_string=10.0.17-MariaDB-log
router_options=mariadb10-compatibility=1,server-id=3,binlogdir=/usr/local/mariadb-maxscale/Binlog_Service

Currently MariaDB 10 compatibility doesn’t show all the MariaDB specific replication events via maxadmin “show services” and may be some fields in MySQL>SHOW SLAVE STATUS should be updated/added.



 Comments   
Comment by Dipti Joshi (Inactive) [ 2015-06-09 ]

Massimiliano Pinto Can you share this for code-review with Markus ?

Comment by Dipti Joshi (Inactive) [ 2015-06-21 ]

Massimiliano Pinto What is documents have been updated for this ?

Please also put link to test case list here.

Thanks,
Dipti

Comment by Dipti Joshi (Inactive) [ 2015-07-06 ]

Massimiliano Pinto, markus makela, tturenko Has this code now merged into develop ?

Generated at Thu Feb 08 03:57:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.