Thanks Chris,
Now it all makes sense. One of my filters is a date range filter with the
current time as a lower range, so it changes with every query. I have just
tried to comment it out and I see the queryResultCache being utilized. I
will try to round the currentTimeMillis down to the nearest mi
Solr version: 3.2.0
--
View this message in context:
http://lucene.472066.n3.nabble.com/queryResultCache-hit-count-is-not-being-increased-when-programmatically-adding-Lucene-queries-as-filt-tp3586892p3586904.html
Sent from the Solr - User mailing list archive at Nabble.com.
In my application I need to deal with a very large number of filter queries
that I cannot pass as http parameters - instead I add them as filters on the
ResponseBuilder:
public void process(ResponseBuilder rb)
{
List filters = rb.getFilters();
if (filters == null) {
Use the following query:
/select?q=*:*&rows=0&wt=json&indent=true&fl=NOT_IMPORTANT&facet=true&facet.zeros=false&fq={!tag=mk
q.op=OR}make:(Ford red 2010)&fq={!tag=cl q.op=OR}color:(Ford red
2010)&fq={!tag=yr q.op=OR}year:(Ford red 2010)&facet.field={!ex=cl,yr
key=mk}make&facet.field={!ex=mk,yr k
