I think there is an issue here, but I didn't follow the TokenStream improvements very closely.

In Solr, CapitalizationFilterFactory has a CharArray set that it loads up with keep words - it then checks (with the old TokenStream API) each token (char array) to see if it should keep it. I think because of the cloning going on in next, this breaks and you can't match anything in the keep set. Does that make sense?

--
- Mark

http://www.lucidimagination.com




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

Reply via email to