Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.4.3
-
None
Description
I notice on maxscale 1.4.3.1-1:
2016-05-03T10:23:06.192082+02:00 host.example.com maxscale[52773]: Unexpected query from 'user'@'10.a.b.c': SET NAMES utf8mb4
The binlog router accepts some other character sets and I am moving to use full unicode support via utf8mb4 but currently this is not understood.
I think that the binlog router does not need to understand the character set really so you probably need to just accept this command and not generate a warning/error like you do for other character sets. If you need to handle the character set then that needs looking at.
This does not seem to be a big deal but does lead to more logging that would be desirable.
In fact probably you should accept any SET NAMES XXXXX command if you don't need to deal with character sets and if you do then handle those you can.