lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (SOLR-5057) queryResultCache should not related with the order of fq's list
Date Tue, 30 Jul 2013 11:59:53 GMT


Erick Erickson commented on SOLR-5057:

You can certainly submit the patch. So take Yonik's version,
put it in your code and try your test.

Then, please run the entire test suite (i.e. execute
'ant clean test' from the root).

But sure, then you can submit the patch. I think Yonik's
version address Hoss's comments, it seems to me that this
patch preserves efficiency without having to make it
a several step operation to handle this case.
> queryResultCache should not related with the order of fq's list
> ---------------------------------------------------------------
>                 Key: SOLR-5057
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 4.0, 4.1, 4.2, 4.3
>            Reporter: Feihong Huang
>            Assignee: Erick Erickson
>            Priority: Minor
>         Attachments: SOLR-5057.patch, SOLR-5057.patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> There are two case query with the same meaning below. But the case2 can't use the queryResultCache
when case1 is executed.
> case1: q=*:*&fq=field1:value1&fq=field2:value2
> case2: q=*:*&fq=field2:value2&fq=field1:value1
> I think queryResultCache should not be related with the order of fq's list.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message