[
https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198177#comment-13198177
]
Robert Muir commented on SOLR-1726:
-----------------------------------
{quote}
on a quick test, I'm getting a maxScore=NaN
{quote}
>From the lucene point of view,
for the first page, because scoredoc = null, this is set (in fact ordinary
collector is used)
for subsequent pages, searchAfter never sets this in the TopDocs, it would just
be telling you something you already know! (and cost extra cpu per collect)
> 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 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]
