Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <20041106061603.66751.qmail@web20926.mail.yahoo.com>
Date: Fri, 5 Nov 2004 22:16:03 -0800 (PST)
From: Jeff Patterson <lucene-list-dev@webdoyen.com>
Reply-To: lucene-list-dev@webdoyen.com
Subject: Pluggable Lock Framework - how to submit code enhancement?
To: Lucene Developers List <lucene-dev@jakarta.apache.org>
In-Reply-To: <20041031173428.GB25978@localharvest.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I've been lurking here as a watcher for a while, but
this is my first post - make this an official "hi!"

We use Lucene at work on a HA system across 2
machines with multiple JVMs accessing the same
NFS-mounted index directory.  We overcame the
NFS locking deficiencies in Lucene by wrapping
the Lucene API calls in a home-grown database
locking mechanism.  I have since hooked up to
the CVS tree for the 1.5 candidate and have
built in to the codebase a pluggable Lock
Override framework allowing a user to build their
own locking mechanism (if you don't, it defaults
to the current filesystem Lock).

This framework seems like it would be beneficial
to the larger community.  What is the best way
for me to get the changes incorporated in to the
next release?  I slightly modified:

  org.apache.lucene.store.FSDirectory

and added one new small class:

  org.apache.lucene.store.LockFactory

Additional tweaks would be advised around
my changes, but I think they would be minor.

Please advise on proper submission protocol. Is it
Bugzilla, to this list, or other?

Thanks - Jeff

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