RE: Move TrieRange to Core/Module and integration issues

2009-04-13 Thread Uwe Schindler
> > For me it would not be a problem, I would use a FilteredTermEnum and > > subclass it, but would only implement next() and the other abstract > methods > > would be dummies (including difference() returning 1.0f). Only the enum > and > > the term should have a protected access or a getter in thi

Re: Move TrieRange to Core/Module and integration issues

2009-04-13 Thread Michael McCandless
On Mon, Apr 13, 2009 at 12:05 PM, Uwe Schindler wrote: > For me it would not be a problem, I would use a FilteredTermEnum and > subclass it, but would only implement next() and the other abstract methods > would be dummies (including difference() returning 1.0f). Only the enum and > the term shou

RE: Move TrieRange to Core/Module and integration issues

2009-04-13 Thread Uwe Schindler
> > MultiTermQuery has in its protected getEnum() returning > FilteredTermEnum. > > For TrieRange, the return should be changed to TermEnum, it is not > needed to > > have a FilteredTermEnum (FilteredTermEnum is only an implementation, the > > method should return an abstract TermEnum). If this is

Re: Move TrieRange to Core/Module and integration issues

2009-04-13 Thread Mark Miller
Uwe Schindler wrote: MultiTermQuery has in its protected getEnum() returning FilteredTermEnum. For TrieRange, the return should be changed to TermEnum, it is not needed to have a FilteredTermEnum (FilteredTermEnum is only an implementation, the method should return an abstract TermEnum). If this