Thanks for the reply Chris - equals and hashCode are implemented correctly
...
I ended up solving my issue by enabling the PostFilter support in the
frange parser using:
{!frange l=1 u=1 cost=200 cache=false}
This works for me because the queries that use my custom ValueSource are
pretty tightly scoped so the PostFilter only sees a few 1000 docs.
Cheers,
Tim
On Tue, Mar 26, 2013 at 4:18 PM, Chris Hostetter
<hossman_luc...@fucit.org>wrote:
>
> : I have a custom ValueSource that I'd like to use as a filter, something
> : like:
> ...
> : My question is whether I should expect Solr to cache this filter in the
> : filterCache? In other words, is there any reason to expect frange filters
>
> Did you remember to implement consistent and meaningful hashCode() and
> equals(OBject) methods for your custom ValueSource?
>
> Take a look at Solr's QueryEqualityTest for examples of how to write tests
> to sanity check that custom QParsers and ValueSourceParsers produce
> Queries and ValueSources that are equivilent (and therfore will produce
> cache hits) when you expect them to.
>
>
>
> -Hoss
>
