I don't think it has to be quite so bleak as that, depending upon the number of queries done over a given timeframe, and the size of the result sets. Solr does cache the identifiers of "documents" returned by search results. See http://wiki.apache.org/solr/SolrCaching paying particular attention to queryResultCache and queryResultWindoeSize . Not a guarantee, of course, but if the number of people searching is limited, and the result set sizes is manageable, the cache can probably accommodate their business need.
JRJ -----Original Message----- From: lee carroll [mailto:lee.a.carr...@googlemail.com] Sent: Thursday, August 25, 2011 6:33 AM To: solr-user@lucene.apache.org Subject: Re: Best way to anchor solr searches? I don't think solr conforms to ACID type behaviours for its queries. This is not to say your use-case is not important just that its not SOLR's focus. I think its a interesting question but the solution is probably going to involve rolling your own. Something like returning 10000 user docs and caching these in an application cache. pagination occurs in this cache rather than as a solr query with the start param incremented. Maybe offer a refresh data link with repopulates the cache from solr. cheers lee c On 25 August 2011 01:01, arian487 <akarb...@tagged.com> wrote: > If I'm searching for users based on last login time, and I search once, then > go to the second page with a new offset, I could potentially see the same > users on page 2 if the index has changed. What is the best way to anchor it > so I avoid this? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Best-way-to-anchor-solr-searches-tp3282576p3282576.html > Sent from the Solr - User mailing list archive at Nabble.com. >
