lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DM Smith <dmsmith...@gmail.com>
Subject Re: inconsistency/performance trap of empty terms
Date Sat, 30 Oct 2010 16:51:08 GMT

On Oct 30, 2010, at 12:00 PM, Robert Muir wrote:

> On Sat, Oct 30, 2010 at 11:54 AM, Yonik Seeley
> <yonik@lucidimagination.com> wrote:
>> If it's only for the QP, a simple method that one could override would suffice:
>> QueryParser.getTokenStream(String field, String value)
>> 
>> If it's not just for the QP, then we have Analyzer (as you've pointed out).
>> 
>> 
> 
> right, but if we did this, it makes some things tricky (e.g. the user
> has to manage reset(Reader)/reset() tokenStream reuse).
> A tokenizer/tokenfilter they are using could be "heavy" in terms of
> initialization cost.

Maybe I'm missing something here. Can't there be an empty analyzer that takes a TokenStream
as an argument to its constructor and wraps it with all the reuse goodness?

> 
> anyway, i'd like to get rid of Analyzer just as much as anyone, but
> making the API difficult/fragile/non-performant isn't a good way



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message