lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-1726) Deep Paging and Large Results Improvements
Date Thu, 13 Oct 2011 17:05:12 GMT


David Smiley commented on SOLR-1726:

I've been following these "large result handling" related issues with some interest. I think
there are some types of applications, the ones that I see at work, where the client essentially
wants to process the entire results from Solr, ideally in a streaming manner.  Paging (that
is, making multiple requests of the dataset to Solr) would ideally not happen because it's
kind of a pain and there are session / stateless issues and efficiency ones.  Ideally Solr
would allow SolrJ to stream the results. Aggregate information like facets would need to be
calculated and retrievable up front, but anything per-document like the document's stored
fields that were asked for and highlighting would be streamed.  What do you guys think of
> Deep Paging and Large Results Improvements
> ------------------------------------------
>                 Key: SOLR-1726
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 3.5, 4.0
> There are possibly ways to improve collections of "deep paging" by passing Solr/Lucene
more information about the last page of results seen, thereby saving priority queue operations.
  See LUCENE-2215.
> There may also be better options for retrieving large numbers of rows at a time that
are worth exploring.  LUCENE-2127.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message