Background: I need to find items matching keywords provided by user, filtered by availability within certain radius from his location & filtered by other user specific params.
So I think this may be very relevant for me because my filter queries may be very unique all the time(since I am filtering by geospatial search, people find items nearest to them). Also some additional user specific filters. So filter queries will always be unique, but the people may use common keywords to lookup, so main query (q param) may be common most times. So if queryResultCache contain all the results returned by main query(q param) , as before filtering then only I think this queryResultCache may be helpful for me. Isn't it ? On Sun, Oct 6, 2013 at 7:13 PM, Erick Erickson <erickerick...@gmail.com>wrote: > First, why is it important to you? General background or a specific > problem you're trying to address? > > But to answer, no. The queryResultCache contains the top N > ids for the query. You control N by setting <queryResultWindowSize> > in solrconfig.xml. It's often set to 2x the usual "rows" parameter > on the theory that people rarely page past the second page. > > Best, > Erick > > On Sun, Oct 6, 2013 at 5:22 AM, Ertio Lew <ertio...@gmail.com> wrote: > > Does the queryResultCache, contain all the results returned by main > query(q > > param) or it contains results prepared after all filter queries ? >
