[
https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126626#comment-13126626
]
Grant Ingersoll commented on SOLR-1726:
---------------------------------------
bq. Having the user pass these in seems very error prone.
How else would we do it? You don't want Solr keeping state, IMO.
bq. They also aren't going to know when the searcher changes (and the internal
docid is invalidated).
I was thinking it would be the external Unique ID, not Lucene's internal id,
which would mean there would have to be a lookup. And, yes, you are correct
they wouldn't know when the searcher changes, but you have that issue already
with paging, so it is no worse than the existing case.
bq. Also, it's not just pageScore that would need to be passed, but a list of
the sort values (which we don't even support returning yet).
right, we would have to add that support to Lucene first. For Solr, we would
need to pass in either the score or the value.
> 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]
