Thank you, Erick! Three great answers!
On Wed, Feb 13, 2013 at 4:20 AM, Erick Erickson <erickerick...@gmail.com>wrote: > First, it may not be a problem assuming your other filter queries are more > frequent. > > Second, the easiest way to keep these out of the filter cache would be just > to include them as a MUST clause, like > +(original query) +id:(1 2 3 4). > > Third possibility, see https://issues.apache.org/jira/browse/SOLR-2429, > but > the short form is: > fq={!cache=false}restoffq > > > On Mon, Feb 11, 2013 at 2:41 PM, Isaac Hebsh <isaac.he...@gmail.com> > wrote: > > > Hi everyone. > > > > I have queries that should be bounded to a set of IDs (the uniqueKey > field > > of my schema). > > My client front-end sends two Solr request: > > In the first one, it wants to get the top X IDs. This result should > return > > very fast. No time to "waste" on highlighting. this is a very standard > > query. > > In the aecond one, it wants to get the highlighting info (corresponding > to > > the queried fields and terms, of course), on those documents (may be some > > sequential requests, on small "bulks" of the "full" list). > > > > These two requests are implemented as almost identical calls, to > different > > requestHandlers. > > > > I thought to append a filter query to the second request, "id:(1 2 3 4 > 5)". > > Is this idea good for Solr? > > If does, my problem is that I don't want these filters to flood my > > filterCache... Is there any way (even if it involves some coding...) to > add > > a filter query which won't be added to filterCache (at least, not instead > > of "standard" filters)? > > > > > > Notes: > > 1. It can't be assured that the the first query will remain in > > queryResultsCache... > > 2. consider index size of 50M documents... > > >
