David Smiley created SOLR-6318:
----------------------------------
Summary: QParser for TermsFilter
Key: SOLR-6318
URL: https://issues.apache.org/jira/browse/SOLR-6318
Project: Solr
Issue Type: New Feature
Components: query parsers
Reporter: David Smiley
Assignee: David Smiley
Fix For: 4.10
Some applications require filtering documents by a large number of terms. It's
often related to security filtering. Naively this is done this way:
{noformat}
fq={!df=myfield q.op=OR}code1 code2 code3 code4 code5...
{noformat}
And this ends up being a BooleanQuery. Users then wind up hitting
BooleaQuery.maxClauseCount (sometimes in production, sadly) and they up it to a
huge number to get the job done.
Solr should offer a QParser based on TermsFilter. I propose it be named
"terms" (plural of term), and have a "separator" option defaulting to a space.
When it's a space, the values also get trimmed, which wouldn't otherwise
happen. The analysis logic should be the same as that for "term" QParser which
is to call FieldType.readableToIndexed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
