Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of DORONC@il.ibm.com designates
 195.212.29.151 as permitted sender)
In-Reply-To: <4547A855.4090706@apache.org>
Subject: Re: lock path thoughts
To: java-dev@lucene.apache.org
Message-ID: 
 <OFD6553EDD.0B2960CE-ON88257218.007AB2A3-88257218.007B1906@il.ibm.com>
From: Doron Cohen <DORONC@il.ibm.com>
Date: Tue, 31 Oct 2006 14:24:33 -0800
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII

Doug Cutting wrote:
> I think the need for that would disappear if the lockless commit patch
> gets committed.  Then there'd be no reason not to put lock files
> directly in the index directory, since only writers would need to lock
> things.

Great! and so we also get rid of this risk:

> .. source for possible problems, when users mis configure
> their lock prefixes. - if the index path was not configured
> correctly, the index would not be found, and this is likely
> to be found and fixed pretty soon. But if lock path prefixes
> are misconfigured, chances are that the index would get corrupted.

So this is an additional advantage of lock-less commits (patch 701).


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org