lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-5610) Add Terms min/max
Date Mon, 21 Apr 2014 14:18:15 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael McCandless updated LUCENE-5610:
---------------------------------------

    Attachment: LUCENE-5610.patch

Another iteration, fixing all nocommits.  I think it's ready ...

I moved the seekCeil impl into a private subclass of FilteredTermsEnum, only for the numeric
case: it's too scary thinking about seeking a FuzzyTermsEnum!

I also added sugar static methods to get the min/max int/long from a Terms.

Finally, I fixed BlockTreeWriter/Reader to save the min and max term.

> 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, 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