You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2019/05/12 20:37:00 UTC
[jira] [Resolved] (LUCENE-7697) IndexSearcher should leverage index
sorting
[ https://issues.apache.org/jira/browse/LUCENE-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand resolved LUCENE-7697.
----------------------------------
Resolution: Duplicate
Oops, actually I've done what I had in mind in LUCENE-8059, I had probably forgotten about this issue. I think this is what your (2) is about.
Regarding (1), we have an open issue about this idea at LUCENE-7714. (It talks about range queries, but it is the same idea as what you are describing for exact matches.)
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org