lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frederik Kraus (JIRA)" <>
Subject [jira] Commented: (SOLR-2386) Filter Query Cache Improvement
Date Sun, 27 Feb 2011 21:12:37 GMT


Frederik Kraus commented on SOLR-2386:

Maybe the easiest way for now is to add some kind "warning" to the wiki/documentation:

1. How filter queries are cached
2. To increase cache hits and reduce "duplicate" fq's -> sort terms in the client

> Filter Query Cache Improvement
> ------------------------------
>                 Key: SOLR-2386
>                 URL:
>             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.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message