lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frederik Kraus (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-2386) Filter Query Cache Improvement
Date Sat, 26 Feb 2011 19:49:58 GMT

     [ https://issues.apache.org/jira/browse/SOLR-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Frederik Kraus updated SOLR-2386:
---------------------------------

          Description: 
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?

  was:
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 54321)

vs

fq=id:(54321 OR 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?

    Affects Version/s:     (was: 1.4.1)
                           (was: 3.1)
                       3.2

> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message