jira at apache
May 16, 2012, 5:31 AM
Post #1 of 1
(38 views)
Permalink
|
|
[jira] [Resolved] (LUCENE-3514) deep paging with Sort
|
|
[ https://issues.apache.org/jira/browse/LUCENE-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-3514.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.0
> deep paging with Sort
> ---------------------
>
> Key: LUCENE-3514
> URL: https://issues.apache.org/jira/browse/LUCENE-3514
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 3.4, 4.0
> Reporter: Robert Muir
> Assignee: Michael McCandless
> Labels: gsoc2012, lucene-gsoc-12
> Fix For: 4.0
>
> Attachments: LUCENE-3514.patch, LUCENE-3514.patch
>
>
> We added IS.searchAfter(Query, Filter) but we don't support Sort yet with this API.
> I think it might be overkill at least at first to try to implement 12 collector variants for this.
> I put the following idea on SOLR-1726:
> 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.
--
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: dev-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene
|
