No, there's nothing like that in Solr. The closest you
could come would be to not do a hard commit (openSearcher=true)
or a soft commit for a very long time. As long as neither
of these things happen, the search results won't
change. But that's a hackish solution.
In fact I question your basic assumption. You say you don't
want the search results to change. But....
1> the user probably wouldn't notice
2> this can mislead in completely different ways. What if
most of the search results were deleted after the
first query? What if the _exact_ document she was
looking for got indexed after the first query?
This is one of those features that at first blush sounds
somewhat reasonable, but I don't think stands up under
inspection. It'd be some amount of work for, IMO, dubious
utility.
If you _must_ do something like this, the app layer could
do something like request a &rows=1000&fl=id
and essentially re-implement the queryResultCache at the
app layer. Subsequent pages would cause you to issue
queries like id=(1 or 54 or 90 ....).
Best
Erick
On Thu, Aug 22, 2013 at 6:00 PM, Ahmet Arslan <iori...@yahoo.com> wrote:
> Hi jfeist,
>
> Your mail reminds me this blog, not sure about solr though.
>
>
> http://blog.mikemccandless.com/2011/11/searcherlifetimemanager-prevents-broken.html
>
>
>
> ________________________________
> From: jfeist <jfe...@llminc.com>
> To: solr-user@lucene.apache.org
> Sent: Friday, August 23, 2013 12:09 AM
> Subject: Storing query results
>
>
> I am in the process of setting up a search application that allows the user
> to view paginated query results. The documents are highly dynamic but I
> want the search results to be static, i.e. I don't want the user to click
> the next page button, the query reruns, and now he has a different set of
> search results because the data changed while he was looking through it. I
> want the results stored somewhere else and the successive page queries to
> draw from that. I know Solr has query result caching, but I want to store
> it entirely. Does Solr provide any functionality like this? I imagine it
> doesn't, because then you'd need to specify how long to store it, etc. I'm
> using Solr 4.4.0. I found someone asking something similar here
> <http://lucene.472066.n3.nabble.com/storing-results-td476351.html> but
> that was 6 years ago.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Storing-query-results-tp4086182.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
