[SOLR-5057] queryResultCache should not related with the order of fq's list

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0, 4.1, 4.2, 4.3
• Fix Version/s: 4.5, 6.0
• Component/s: search
• Assignee: Erick Erickson
• Reporter: Feihong Huang
• Created: 22/Jul/13 13:17
• Updated: 03/May/17 03:49
• Resolved: 21/Aug/13 21:24

Description

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.

Issue Links

• breaks: SOLR-5618 false query result cache hits possible when duplicate filter queries exist in one query -- discovered via: Reproducible failure from TestFiltering.testRandomFiltering
• is duplicated by: SOLR-2716 QueryResultKey hashCode() and equals() is dependent on filter order