I think this is more a result of the Tokenizer on top, does not correctly implementing end(). In Lucene 4.6 you will get much better error messages (IllegalStateException) because we improved this detection, also during runtime.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Benson Margulies [mailto:ben...@basistech.com] > Sent: Wednesday, October 30, 2013 12:30 AM > To: java-user@lucene.apache.org > Subject: new consistency check for token filters in 4.5.1 > > My token filter has no end() method at all. Am I required to have an end > method()? > > BaseLinguisticsTokenFilterTest.testSegmentationReadings:175- > >Assert.assertTrue:41->Assert.fail:88 > super.end()/clearAttributes() was not called correctly in end() > > BaseLinguisticsTokenFilterTest.testSpacesInLemma:189- > >Assert.assertTrue:41->Assert.fail:88 > super.end()/clearAttributes() was not called correctly in end() --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
