ednesday, June 30, 2010 10:34 AM
> > To: [email protected]
> > Subject: Re: [CLucene-dev] IndexModifier exception during destruction
> >
> > 2010/6/17 Itamar Syn-Hershko :
> > > You can send it on the mailing list, or to me privately. Either as a c
ubject: Re: [CLucene-dev] IndexModifier exception during destruction
>
> 2010/6/17 Itamar Syn-Hershko :
> > 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
2010/6/17 Itamar Syn-Hershko :
> 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 bi
To: [email protected]
> Subject: Re: [CLucene-dev] IndexModifier exception during destruction
>
> I have test ready, but I'm not sure where (and how) to upload it?
> Borek
>
> > -Original Message-
> > From: Itamar Syn-Hershko [mailto:ita...@d
e-dev] IndexModifier exception during destruction
>
> Would love one, thanks.
>
> Itamar.
>
> > -Original Message-
> > From: Kostka Bořivoj [mailto:[email protected]]
> > Sent: Wednesday, June 16, 2010 6:49 PM
> > To: [email protected]
Would love one, thanks.
Itamar.
> -Original Message-
> From: Kostka Bořivoj [mailto:[email protected]]
> Sent: Wednesday, June 16, 2010 6:49 PM
> To: [email protected]
> Subject: Re: [CLucene-dev] IndexModifier exception during destruction
>
> To: [email protected]
> Subject: Re: [CLucene-dev] IndexModifier exception during destruction
>
> You are right, thanks. This is how JL does this too. I fixed this and
> committed to git as e75f0c...22e4 [1].
>
> Do you have a way of reproducing thi
tka Bořivoj [mailto:[email protected]]
> Sent: Wednesday, June 16, 2010 12:08 PM
> To: [email protected]
> Subject: [CLucene-dev] IndexModifier exception during destruction
>
> After an unsuccesfull call of IndexModifier::addDocument
> (catched exc
After an unsuccesfull call of IndexModifier::addDocument (catched exception
"Lock obtain timed out"), IndexModifier destructor causes Accesss violation
exception.
This is beacause after unsuccessfull call to addDocument both members
indexReader and indexWriter are NULL, but the check of indexRe