You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/24 22:18:39 UTC

[jira] [Commented] (LUCENE-5610) Add Terms min/max

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

ASF subversion and git services commented on LUCENE-5610:
---------------------------------------------------------

Commit 1613268 from [~mikemccand] in branch 'dev/trunk'
[ https://svn.apache.org/r1613268 ]

LUCENE-5610: optimization: just use already allocated/copied PendingTerm to for min/maxTerm

> 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
>             Fix For: 4.9, 5.0
>
>         Attachments: LUCENE-5610.patch, 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