Yes, you are right, under 2_3_2 this will never throw exception. I'll modify the test Thanks.
Borek > -----Original Message----- > From: Veit Jahns [mailto:nuncupa...@googlemail.com] > Sent: Wednesday, June 30, 2010 10:34 AM > To: clucene-developers@lists.sourceforge.net > Subject: Re: [CLucene-dev] IndexModifier exception during destruction > > 2010/6/17 Itamar Syn-Hershko <ita...@divrei-tora.com>: > > You can send it on the mailing list, or to me privately. Either as a code > > file, or (ultimately) a patch for cl_test introducing the new test case. > > I saw this test (IndexModifierExceptionTest) on the git repository. > But the IndexModifier of 2_3_2 works a little bit different than the > IndexModifier of 0.9.21. In 2_3_2 the IndexWriter is opend during the > initialization of IndexModifier. addDocument will never throw a > timeout exception, because the embedded IndexWriter holds the lock > already. If not, the timeout exception will be thrown during the > initialization of the IndexModifier and addDocument will be never > called. I.e., directory.errOn should be setted to true before the > construction of the IndexModifier. > > Veit > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > CLucene-developers mailing list > CLucene-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/clucene-developers ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ CLucene-developers mailing list CLucene-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clucene-developers
