binlog_router disconnects client after wrong sql

Hi,

i use two different Python MySQL connectors, which both run sql commands right after the inital connection, like:

set autocommit=0

or

SET @@session.autocommit = OFF

MaxScale does not support the sql from above and prints an error:

error  : Unexpected query from 'nagios'@'1.2.3.4': set autocommit=0

notice : my_binlog: Slave 1.2.3.4, server id 0, disconnected after 0 seconds. 1 SQL commands

This prevents me from getting the slave status via python scripts from maxscale binlog router.

Couldn't this just be a warning instead of disconnecting a slave with wrong sql? Maybe the problem is related to the python connector rather than maxscale.

Regards, Michael