[
https://issues.apache.org/jira/browse/LUCENE-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838371#comment-16838371
]
Adrien Grand commented on LUCENE-7697:
--------------------------------------
I am not, but [~jtibshirani] recently mentioned to me that she'd like to look
into LUCENE-7714. There is LUCENE-8727 which is somewhat related too: some of
the optimizations that we apply based on the minimum competitive score, and to
a lesser extent index sorting, become less efficient when IndexSearcher is
configured with an executor. This is due to the fact that these optimizations
leverage information about already collected documents to more efficiently
collect new documents. Since IndexSearcher searches each slice independently, a
given slice can't benefit from information that has been collected in other
slices.
> IndexSearcher should leverage index sorting
> -------------------------------------------
>
> Key: LUCENE-7697
> URL: https://issues.apache.org/jira/browse/LUCENE-7697
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
>
> We made good efforts in order to make index sorting fast and easy to
> configure. We should now look into making IndexSearcher aware of it. This
> will probably require changes of the API as not collecting all matches means
> that we can no longer know things like the total number of hits or the
> maximum score.
> I don't plan to work on it anytime soon, I'm just opening this issue to raise
> awareness. I'd be happy to do reviews however if someone decides to tackle it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
