[SOLR-16199] Solr SQL using {!complexphrase} for wildcard filters doesn't always work as expected - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 8.11.2, 9.1
Component/s: Parallel SQL
Labels:
- RobustSQL

Description

If a field is text analyzed, then doing {{

{!complexphrase}

name:\"Test*\"}} causes:

\"msg\":\"maxClauseCount is set to 1024\",\n    \"trace\":\"org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024\\n\\tat

Working around the issue with the parens hack like name LIKE '(Test*)' makes the query work as expected. Perhaps we can just drop using the complexphrase parser if the predicate has a trailing wildcard only (leading too), that'll probably cover the bulk of the problems and use parens instead of double quotes if it has multiple wild card in it?

Need to build some better test cases around wildcard matching for string and text analyzed fields.