[jira] [Resolved] (SOLR-1726) Deep Paging and Large Results Improvements

["Hoss Man (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man resolved SOLR-1726.
----------------------------

       Resolution: Incomplete
    Fix Version/s:     (was: 4.6)
                   4.0

Since all of the existing code attached to this issue was committed prior to 4.0 -- but then nearly immediately disabled by commenting out the key bits in QParser.getPaging() -- i think attempting to continue building off this existing issue would just be confusing.

I'm marking this issue as "Resolution: Incomplete" and I've opened a new issue (SOLR-5463) to track new development towards this goal

> 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.0
>
>         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