You could copy the existing core to a new core every once in awhile, and then do your delta indexing into a new core once the copy is complete. If a Persistent URL for the search results included the name of the original core, the results you would get from a bookmark would be stable. However, if you went to the site, and did a new site, you would be searching the newest core.
This I think applies whether the site is "Intranet" or not. Older cores could be aged out gracefully, and the search handler for an old core could be replaced by a search on the new core via sharding. On Fri, Aug 23, 2013 at 11:57 AM, jfeist <jfe...@llminc.com> wrote: > I completely agree. I would prefer to just rerun the search each time. > However, we are going to be replacing our rdb based search with something > like Solr, and the application currently behaves this way. Our users > understand that the search is essentially a snapshot (and I would guess > many > prefer this over changing results) and we don't want to change existing > behavior and confuse anyone. Also, my boss told me it unequivocally has to > be this way :p > > Thanks for your input though, looks like I'm going to have to do something > like you've suggested within our application. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Storing-query-results-tp4086182p4086349.html > Sent from the Solr - User mailing list archive at Nabble.com. >
