[
https://issues.apache.org/jira/browse/SOLR-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720397#comment-13720397
]
Hoss Man commented on SOLR-5057:
--------------------------------
Similar to yoniks point initial point: In my experience, the situations where
folks are going to be most concerned about having good cache usage are the
situations where queries are generated programatically and the order of the
filter queries is already deterministic (or can be made deterministic easy
enough by the client)
My straw man suggestion would be to not modify QueryResultKey at all, and
instead write a new (optional) SearchComponent that did nothing by sort the
getFilters() array in it's prepare() method. Users who can't ensure that
requests with equivalent "fq" params queries come in the same order can
register it to run just after the "query" component and get good cache hit
ratios, but it wouldn't affect the performance in any way for users who send
queries with fqs i na determinstic manner
> queryResultCache should not related with the order of fq's list
> ---------------------------------------------------------------
>
> Key: SOLR-5057
> URL: https://issues.apache.org/jira/browse/SOLR-5057
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
