[
https://issues.apache.org/jira/browse/LUCENE-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5610:
--------------------------------
Attachment: LUCENE-5610.patch
Here is a prototype. I think codecs like blocktree could just override and
probably get the maximum value in constant time.
This stuff is probably most useful for numeric fields, but unfortunately they
add extra terms, and their termsenums aren't seekable. So maybe
NumericUtils.filterPrefixCoded* can be fixed to return "real" termsenums rather
than FilteredTermsEnum?
FilteredTermsEnum is much less useful in general, its pretty much only good for
MultiTermQuery execution.
> Add Terms min/max
> ------------------
>
> Key: LUCENE-5610
> URL: https://issues.apache.org/jira/browse/LUCENE-5610
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Attachments: LUCENE-5610.patch
>
>
> Having upper/lower bounds on terms could be useful for various optimizations
> in the future, e.g. to accelerate sorting (if a segment can't compete, don't
> even search it), and so on.
> Its pretty obvious how to get the smallest term, but the maximum term for a
> field is tricky, but worst case you can do it in ~ log(N) time by binary
> searching term space.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
