Doug:
       My apologies if I came off seeming angry and/or trying to lobby to be
a committer. Neither is the case.

       I am expressing a concern with how patches are being handled with
this project, and providing my view point on how this can be better managed.
Of course my concern can be either accepted or rejected. I just hope the
committers would be "calm" enough to be able to see criticisms for what they
are.

       I am a strong advocate of Lucene, hence my passion for its success.

-John

On Wed, Dec 3, 2008 at 10:07 AM, Doug Cutting <[EMAIL PROTECTED]> wrote:

> John Wang wrote:
>
>> If you guys need help, maybe you guys should expand your committer list?
>>
>
> Committers are added when they've contributed a series of high-quality
> patches that have been committed, and demonstrated their ability to be easy
> to work with.  Displaying anger is not a good way to become a committer.
>  Calm persistence is advised.
>
> Lucene does not currently use Java Serialization much.  Many committers may
> not be terribly familiar with it.
>
>  Use case: deploying lucene in a distributed environment, we have a
>> broker/server architecture. (standard stuff), we want roll out search
>> servers with lucene 2.4 instance by instance. The problem is that the
>> broker is sending a Query object to the searcher via java
>> serialization at the server level, and the broker is running 2.3. And
>> because of specifically this problem, 2.3 brokers cannot to talk to
>> 2.4 search servers even when the Query object was not changed.
>>
>
> Thanks for providing a use case.  One way to address this would be for
> Lucene to better support cross-version serialization.  Another way might be
> for your application, which adds this requirement, to use an alternate
> representation for queries that it can guarantee is compatible across
> versions, e.g., a string.  Might that be possible?
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to