lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Kaelbling <>
Subject CachingTokenFilter extensibility and LUCENE-1685
Date Thu, 27 Aug 2009 20:39:31 GMT

Looking at Lucene 2.9 trunk, CachingTokenFilter seems much less extensible than before.  In
previous releases I subclassed it so I could back the cache with an array and provide random
access to the stream.  I can't see how to do this any more, and the WeightedSpanTermExtractor.getReaderForField()
is still hardwired to require a CachingTokenFilter-derived object.

Am I missing something?  Having two copies of the token stream, one for random access and
one hidden inside the CachingTokenFilter, does not sound efficient :-)


David Kaelbling
Senior Software Engineer
Black Duck Software, Inc.
T +1.781.810.2041
F +1.781.891.5145
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message