- A clear description of the issue
each time we use mysqldump with a where option this generate a lot of warning messages into proxysql logs.
- ProxySQL version
proxysql 2.5.5-1.2.bullseye
- OS version
Debian 11
- The steps to reproduce the issue
Execute the following mysqldump command :
mysqldump -h server -u user -ppassword database table --where="campaign_id = 10" >> result.sql
- The full ProxySQL error log
Sep 18 10:34:27 server proxysql 2024-09-18 10:34:19 MySQL_Session.cpp:7954:unable_to_parse_set_statement(): [WARNING] Unable to parse unknown SET query from client 192.168.1.1:39284. Setting lock_hostgroup. Please report a bug for future enhancements:/*!100100 SET @@MAX_STATEMENT_TIME=0.000000 */
Not sure this is a bugplease let me know if you need more information.
I can reproduce the issue if needed.
Indeed, at the moment proxysql doesn't parse SET statements inside comments (with exclamation mark).
Thank you for the report, we will look into further improvement in the future releases.
- A clear description of the issue each time we use mysqldump with a where option this generate a lot of warning messages into proxysql logs.
- ProxySQL version proxysql 2.5.5-1.2.bullseye
- OS version Debian 11
- The steps to reproduce the issue
Execute the following mysqldump command :
mysqldump -h server -u user -ppassword database table --where="campaign_id = 10" >> result.sql
- The full ProxySQL error log
Sep 18 10:34:27 server proxysql 2024-09-18 10:34:19 MySQL_Session.cpp:7954:unable_to_parse_set_statement(): [WARNING] Unable to parse unknown SET query from client 192.168.1.1:39284. Setting lock_hostgroup. Please report a bug for future enhancements:/*!100100 SET @@MAX_STATEMENT_TIME=0.000000 */
Not sure this is a bugplease let me know if you need more information. I can reproduce the issue if needed.