lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (Jira)" <>
Subject [jira] [Commented] (LUCENE-7282) search APIs should take advantage of index sort by default
Date Tue, 10 Sep 2019 19:09:00 GMT


Atri Sharma commented on LUCENE-7282:

I think LUCENE-7714 does a similar thing for range queries. However, I don’t think we do
this optimisation for exact queries yet (I might be mistaken though, [~jtibshirani] any thoughts

> search APIs should take advantage of index sort by default
> ----------------------------------------------------------
>                 Key: LUCENE-7282
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message