> -----Original Message----- > From: Fergus McMenemie [mailto:fer...@twig.me.uk] > Sent: Friday, June 12, 2009 3:41 PM > To: solr-user@lucene.apache.org > Subject: Re: fq vs. q > > >On Fri, Jun 12, 2009 at 7:09 PM, Michael Ludwig <m...@as-guides.com> > wrote: > > > >> I've summarized what I've learnt about filter queries on this page: > >> > >> http://wiki.apache.org/solr/FilterQueryGuidance > >> > > > >Wow! This is great! Thanks for taking the time to write this up > Michael. > > > >I've added a section on analysis, scoring and faceting aspects. > >
+1 definitely a great article I ran into this very issue recently as we are using a "freshness" filter for our data that can be 6//12/18 months etc. I discovered that even though we were only indexing with day-level granularity, we were specifying the query by computing a date down to the second and thus virutally every filter was unique. It's amazing how something this simple could bring solr to it's knees on a large data set. By simply changing the filter to "date:[NOW-18MONTHS TO NOW]" or equivalent, the problem vanishes. It does bring up an interestion question though - how is "NOW" treated wrt to the cache key? Does solr translate it to a date first? If so, how does it determine the granularity? If not, is there any mechanism to flush the cache when the corresponding result set changes? -Ken
