[
https://issues.apache.org/jira/browse/LUCENE-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3225:
---
Attachment: LUCENE-3225.patch
OK, new patch: I added a new seekExact method (instead of new boolean to seek);
renamed existing seek methods to either seekCeil or seekExact; changed
seekExact(long ord) to not return a value (it's an error to pass out-of-bounds
ord to this method). I think it's ready!
> Optimize TermsEnum.seek when caller doesn't need next term
> --
>
> Key: LUCENE-3225
> URL: https://issues.apache.org/jira/browse/LUCENE-3225
> Project: Lucene - Java
> Issue Type: Improvement
>Reporter: Michael McCandless
>Assignee: Michael McCandless
> Fix For: 4.0
>
> Attachments: LUCENE-3225.patch, LUCENE-3225.patch
>
>
> Some codecs are able to save CPU if the caller is only interested in
> exact matches. EG, Memory codec and SimpleText can do more efficient
> FSTEnum lookup if they know the caller doesn't need to know the term
> following the seek term.
> We have cases like this in Lucene, eg when IW deletes documents by
> Term, if the term is not found in a given segment then it doesn't need
> to know the ceiling term. Likewise when TermQuery looks up the term
> in each segment.
> I had done this change as part of LUCENE-3030, which is a new terms
> index that's able to save seeking for exact-only lookups, but now that
> we have Memory codec that can also save CPU I think we should commit
> this today.
> The change adds a "boolean onlyExact" param to seek(BytesRef).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
