You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexander S. (JIRA)" <ji...@apache.org> on 2014/12/26 18:20:15 UTC

[jira] [Commented] (SOLR-6494) Query filters applied in a wrong order

    [ https://issues.apache.org/jira/browse/SOLR-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259150#comment-14259150 ] 

Alexander S. commented on SOLR-6494:
------------------------------------

Just an idea, but what if Solr detecting that the filter does use date rages like [* TO 2014-09-08T23:59:59Z] (or probably any ranges were cache is not very efficient), and if there are other simpler filters in the query, will apply such range filters at last? And probably to already fetched results as a post filter? And probably avoid caching for this filter? That sounds like a good optimization to me. This will avoid losing of more useful filters from the cache, increase warming speed and which is the most important — increase the search speed. [~erickerickson] [~hossman]

Best,
Alex

> Query filters applied in a wrong order
> --------------------------------------
>
>                 Key: SOLR-6494
>                 URL: https://issues.apache.org/jira/browse/SOLR-6494
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.8.1
>            Reporter: Alexander S.
>
> This query:
> {code}
> {
>   fq: ["type:Award::Nomination"],
>   sort: "score desc",
>   start: 0,
>   rows: 20,
>   q: "*:*"
> }
> {code}
> takes just a few milliseconds, but this one:
> {code}
> {
>   fq: [
>     "type:Award::Nomination",
>     "created_at_d:[* TO 2014-09-08T23:59:59Z]"
>   ],
>   sort: "score desc",
>   start: 0,
>   rows: 20,
>   q: "*:*"
> }
> {code}
> takes almost 15 seconds.
> I have just ≈12k of documents with type "Award::Nomination", but around half a billion with created_at_d field set. And it seems Solr applies the created_at_d filter first going through all documents where this field is set, which is not very smart.
> I think if it can't do anything better than applying filters in the alphabet order it should apply them in the order they were received.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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