Bug #3092
Avoid CQP crash when the CQL length limit is reached
Status: | New | Start date: | 06/11/2021 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | - | % Done: | 80% |
||
Category: | SearchEngine | Spent time: | - | ||
Target version: | TXM 0.8.2 |
Description
Since TXM 0.8.0, the CQL string length limit has been set to 16000 to limit CQP (and TXM) crash on long CQL strings.
But there are always new TXM usages that can crash CQP by very long CQL strings.
To definitively avoid TXM crash (memory linked to CQP's memory), add tests on CQL length before calling cqi.cqpQuery() and show an error message that indicates the current TXM CQL string maximum length and the current CQL string length.
History
#1 Updated by Matthieu Decorde about 1 year ago
- Subject changed from aVoid crash when the CQL length limit is reached to Avoid crash when the CQL length limit is reached
#2 Updated by Matthieu Decorde about 1 year ago
- Tracker changed from Task to Bug
#3 Updated by Serge Heiden about 1 year ago
- Subject changed from Avoid crash when the CQL length limit is reached to Avoid CQP crash when the CQL length limit is reached
- Description updated (diff)