lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <>
Subject [jira] Commented: (LUCENE-1473) Implement Externalizable in main top level searcher classes
Date Wed, 03 Dec 2008 20:39:44 GMT


Doug Cutting commented on LUCENE-1473:

> I'm not sure why you and Doug and focusing on performance when that is not really the
main issue I brought up.

In the description of this issue you claim, "This will make Serialization faster".  I only
added that, if this is a motivation, then it should be benchmarked and quantified.  If it's
not a motivation, and cross-version compatibility is the only motivation, then that should
be clarified.

> dynamic classloading is being ignored by you folks

Perhaps most Lucene developers are not using dynamic class loading, just as most Lucene developers
seem not to be relying on java serialization.  Perhaps you can convince them to start using
it, but if not, you may need to find a way to get Lucene to support it that minimally impacts
other users of Lucene.  Adding methods to Term and Query that must be changed whenever these
classes change adds a cost.  If folks don't see much benefit, then that cost outweighs.  Perhaps
you can better enlighten us to the benefits rather than assert willful ignorance?  Jini promised
great things with dynamic class loading, but the list of folks that use Jini is not long (

> Implement Externalizable in main top level searcher classes
> -----------------------------------------------------------
>                 Key: LUCENE-1473
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 2.4
>            Reporter: Jason Rutherglen
>            Priority: Minor
>         Attachments: LUCENE-1473.patch
> To maintain serialization compatibility between Lucene versions, major classes can implement
Externalizable.  This will make Serialization faster due to no reflection required and maintain
backwards compatibility.  

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message