Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 13 Oct 2011 17:05:12 +0000 (UTC)
From: "David Smiley (Commented) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1652543766.9908.1318525512232.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-1726) Deep Paging and Large Results
 Improvements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126727#comment-13126727 ] 

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 this?
                
> Deep Paging and Large Results Improvements
> ------------------------------------------
>
>                 Key: SOLR-1726
>                 URL: https://issues.apache.org/jira/browse/SOLR-1726
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org