Open
Description
Hey Rene,
A clear description of your issue
It seems when a query was broken, it will be logged into query log but uncompleted.
Example:
I found the error log in proxysql.log as below
2018-08-30 23:50:22 MySQL_Session.cpp:2884:handler(): [WARNING] Error during query on (4101,10.0.33.30,3306): 3144, Cannot create a JSON value from a string with CHARACTER SET 'binary'.
In query log, I found the uncompleted query log, believe related to the error log above:
ProxySQL LOG QUERY: thread_id="9380763" username="####" schemaname=####" client="10.0.34.227:3572" HID=NULL starttime="2018-08-30 23:50:22.429817" endtime="2018-08-30 23:50:22.429817" duration=0us digest="0x8EF306302FB86F93" 34.227:3572
The version of OS and ProxySQL
mysql Ver 14.14 Distrib 5.7.23, for Linux (x86_64) using EditLine wrapper
ProxySQL version v1.4.10-1-g5eb0f3e, codename Truls
OS: # lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
Two questions:
- can we get the full query through the digest hashed: digest="0x8EF306302FB86F93" ?
- can we get the full query even the query is broken?