[jira] [Commented] (LUCENE-7282) search APIs should take advantage of index sort by default

["Luca Cavanna (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485861#comment-17485861 ] 

Luca Cavanna commented on LUCENE-7282:
--------------------------------------

I would like to work on this. I was wondering what direction I should take: extend the existing TermQuery and add the optimization around index sorting, or rather introduce a specialized IndexSortTermQuery that could then be leveraged once LUCENE-10162 is worked on?

> search APIs should take advantage of index sort by default
> ----------------------------------------------------------
>
>                 Key: LUCENE-7282
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7282
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Priority: Major
>
> Spinoff from LUCENE-6766, where we made it very easy to have Lucene sort documents in the index (at merge time).
> An index-time sort is powerful because if you then search that index by the same sort (or by a "prefix" of it), you can early-terminate per segment once you've collected enough hits.  But doing this by default would mean accepting an approximate hit count, and could not be used in cases that need to see every hit, e.g. if you are also faceting.
> Separately, `TermQuery` on the leading sort field can be very fast since we can advance to the first docID, and only match to the last docID for the requested value.  This would not be approximate, and should be lower risk / easier.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org