Pluggable Lock Framework - how to submit code enhancement?

[Jeff Patterson <lu...@webdoyen.com>]

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

Re: Pluggable Lock Framework - how to submit code enhancement?

[Otis Gospodnetic <ot...@yahoo.com>]

Official Hi Jeff,

That sounds like something many users would appreciate.  Bugzilla is
the best way to submit your code.  Open a new 'bug' in Bugzilla, prefix
the summary line with [PATCH], and then attach your code.  This will
have to be a 2-step process: 1) open a bug, 2) attach code.  That's
just how Bugzilla works.

Otis

--- Jeff Patterson <lu...@webdoyen.com> wrote:

> 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
> 
> 


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