See the queryResultCache setting in your solrconfig.xml file. For a
given query it keeps a
(configurable) list of results, you could simply make this very large,
at the usual memory
cost.
Best
Erick
On Sun, Jun 19, 2011 at 6:02 PM, Hiller, Dean x66079
wrote:
> As you probably know, using Query
One technique I've used to page through huge result sets that could
help: if you have a sortable key (like an id), you can just fetch all
docs, sorted by the key, and then on subsequent page requests use the
last value from the previous page as a filter in a range term like:
id:[ TO *]
where
As you probably know, using Query in hibernate/JPA gets slower and slower each
page since it starts all over on the index tree :( WHILE ScrollableResultSet
does NOT because the database maintains a cursor into the index that just picks
up where it left off so as you go to the next page, next pag
