[
https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126656#comment-13126656
]
Robert Muir commented on SOLR-1726:
-----------------------------------
yeah from my perspective i would prefer for the API to be 'complete'.
One idea would be to start with one or two implementations (maybe in/out of
order) for the sorting case, and dont overspecialize it yet.
* for page 1, the ScoreDoc (FieldDoc really) will be null, so we just return
the normal impl anyway.
* even if our searchAfter isnt huper-duper fast, the user can always make the
tradeoff like with page-by-score. they can always just pass null until like
page 10 or something if they compute that it only starts to 'help' then.
> 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: [email protected]
For additional commands, e-mail: [email protected]
