lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5610) Add Terms min/max
Date Fri, 18 Apr 2014 19:53:17 GMT

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

Robert Muir commented on LUCENE-5610:
-------------------------------------

{quote}
It's a long shot ... but maybe we could index the "exact" trie terms
in a separate field than their precShifts? Then we could just take
max of the "exact trie terms" field ... that's a big change though
{quote}

I think there is a much simpler solution though, we just dont return FilteredTermsEnum from
that one method, instead a regular termsenum. it just has to look for the special byte prefix
and return END.

Then we can easily do what we want.

> 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, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message