[ https://issues.apache.org/jira/browse/LUCENE-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053964#comment-13053964 ]
Michael McCandless commented on LUCENE-3225: -------------------------------------------- bq. Yet the other should the be seekFloor no? Ahhh right, we had discussed on the dev list. I agree! But, we should do this in another issue. Though, I think we should rename the current seek to seekCeil; I'll do that here. > 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 > > > 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