Hi, 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 :-) Thanks, David -- David Kaelbling Senior Software Engineer Black Duck Software, Inc. dkaelbl...@blackducksoftware.com T +1.781.810.2041 F +1.781.891.5145 http://www.blackducksoftware.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
