QAN errors on large queries
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
AFFECTED CS IDs
274244, CS0028359
is cloned by
Smart Checklist
Activity
Show:

Michael Coburn October 27, 2022 at 3:30 PM
Thank you for explanation , I now see we have addressed this request.
Jiří Čtvrtka October 27, 2022 at 3:23 PMEdited
Its solved by https://jira.percona.com/browse/PMM-8792. If you set limit to -1 query length is unlimited and explain will work every time. Same function is for mongo and pg in 2.32. Something like this will be mention in doc for 2.32. If something was missed just ping me.

Michael Coburn October 27, 2022 at 2:20 PM
Hi -
So was this work actually completed? I don't see any PRs since 2018
Jiří Čtvrtka October 27, 2022 at 7:31 AM
This one can be closed, but I should mention this in doc.

duygu.aksoy October 27, 2022 at 7:21 AM
can we close this one? Or there is more that we need to plan for the next release?
Done
Details
Details
Assignee
Reporter

Priority
Components
Labels
Planned Version/s
Fix versions
Story Points
0
Parent
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created December 22, 2017 at 9:02 AM
Updated November 13, 2024 at 8:32 AM
Resolved October 27, 2022 at 7:32 AM
Query is truncated with .. based on arbitrary length. QAN doesn't deal with it well and not only can you not see the whole query, but underneath, it throws these errors: