You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Scott Stults (JIRA)" <ji...@apache.org> on 2013/10/10 15:41:42 UTC
[jira] [Commented] (SOLR-1726) Deep Paging and Large Results
Improvements
[ https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791495#comment-13791495 ]
Scott Stults commented on SOLR-1726:
------------------------------------
Dmitry, I think "scrolling" would help in the case of Hadoop integration, such as pulling a few hundred thousand docs based off of a query to the local node so that you can do an aggregated calculation with Pig or M/R.
> 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: 4.6
>
> Attachments: CommonParams.java, QParser.java, QueryComponent.java, ResponseBuilder.java, SOLR-1726.patch, SOLR-1726.patch, SolrIndexSearcher.java, TopDocsCollector.java, TopScoreDocCollector.java
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org