Hmm I see only one question? Sure, after pulling a new TermsEnum, you can use .seekExact to position it, instead of next, but you must have a term in mind to "target" when you call seekExact.
seekExact ought to be faster than seekCeil, since it's not required to position the enum if the term was not found. But next() ought to be faster than seekExact; you're seeing the opposite? Mike McCandless http://blog.mikemccandless.com On Wed, Mar 5, 2014 at 12:47 PM, hao yan <[email protected]> wrote: > Hey, guys > > Two questions: > 1. From our experiments, we find next() is very costly. In TermsEnum's > javadoc, it said that > TermsEnum is unpositioned when you first obtain it and you must successfully > call next or one of seek* methods. From my experiments, I find that next() > is costly. > > My question is: > > Can we only use seekExact() and never use seekCeil or next , in order to > improve performance ? > > thanks! > > hao > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
