Re: Possible issue with Tokenizer in lucene-analyzers-common-4.6.1

2014-03-20 Thread Joe Wong
ings. There is a second method in Analyzer that > takes a String to analyze (instead of Reader). This one uses an optimized > workflow internally. > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetap

Re: Possible issue with Tokenizer in lucene-analyzers-common-4.6.1

2014-03-20 Thread Joe Wong
e in addition, because this helps to find out what call sequence you > have. > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Joe Wong [

Possible issue with Tokenizer in lucene-analyzers-common-4.6.1

2014-03-20 Thread Joe Wong
Hi We're planning to upgrade lucene-analyzers-commons 4.3.0 to 4.6.1 . While running our unit test with 4.6.1 it fails at org.apache.lucene.analysis.Tokenizer on line 88 (setReader method). There it checks if input != ILLEGAL_STATE_READER then throws IllegalStateException. Should it not be if inp