nal Message-
>> From: Michael McCandless [mailto:luc...@mikemccandless.com]
>> Sent: Saturday, November 21, 2009 2:10 AM
>> To: java-user@lucene.apache.org
>> Subject: Re: ConcurrentMergeScheduler, Exception and transaction
>>
>> An exception during merging does
e caller needs to be reported of the
> error so that
> > it can ask Lucene and other participants of transaction to
> roll back.
> > Am I missing something?
> >
> > -kuro
> >
> >> -Original Message-
> >> From: Jason Rutherglen [ma
>
>> -Original Message-
>> From: Jason Rutherglen [mailto:jason.rutherg...@gmail.com]
>> Sent: Friday, November 20, 2009 4:14 PM
>> To: java-user@lucene.apache.org
>> Subject: Re: ConcurrentMergeScheduler, Exception and transaction
>>
>> Teruhiko,
>
gt; Subject: Re: ConcurrentMergeScheduler, Exception and transaction
>
> Teruhiko,
>
> The index remains consistent even when a background merge
> fails, meaning commit truly represents a valid index after
> it's called.
> You can share merge schedulers, though in pract
Teruhiko,
The index remains consistent even when a background merge fails,
meaning commit truly represents a valid index after it's called.
You can share merge schedulers, though in practice it's not
going to improve anything.
Jason
2009/11/20 Teruhiko Kurosaka :
> I was experimenting how Lucene
