[
https://issues.apache.org/jira/browse/SOLR-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166113#comment-13166113
]
Mikhail Khludnev commented on SOLR-2386:
----------------------------------------
Doesn't it related to
http://lucene.apache.org/solr/api/org/apache/solr/search/ExtendedQuery.html#getCacheSep%28%29
? For me it looks like if we will have both clauses cached then implement
in-flight OrFilter(DocSet, DocSet) not a big deal.
> Filter Query Cache Improvement
> ------------------------------
>
> Key: SOLR-2386
> URL: https://issues.apache.org/jira/browse/SOLR-2386
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 3.2, 4.0
> Reporter: Frederik Kraus
> Priority: Minor
>
> Currently logically identical filter queries are not reduced to one query,
> but processed and cached individually.
> In terms of cache "keys" the following two, logically identical queries, each
> have a different key:
> fq=id:12345 OR id:54321
> vs
> fq=id:54321 OR id:12345
> Internally both queries should be stored and requested by/from the cache as
> fq=id:(12345 OR 54321) i.e. the clauses in BooleanQuery should be sorted.
> Not sure where this would fit best. Lucene/BooleanQuery looks like a natural
> place to do this sort, but might be more a solr optimization?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
