[
https://issues.apache.org/jira/browse/LUCENE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653378#action_12653378
]
John Wang commented on LUCENE-1473:
-----------------------------------
Mike:
If you have class A implements Serializable, with a defined suid, say 1.
Let A2 be a newer version of class A, and suid is not changed, say 1.
Let's say A2 has a new field.
Imaging A is running in VM1 and A2 is running in VM2. Serialization
between VM1 and VM2 of class A is ok, just that A will not get the new fields.
Which is fine since VM1 does not make use of it.
You can argue that A2 will not get the needed field from serialized A,
but isn't that better than crashing?
Either the case, I think the behavior is better than it is currently.
(maybe that's why Eclipse and Findbug both report the lacking of suid
definition in lucene code a warning)
I agree adding Externalizable implementation is more work, but it would
make the serialization story correct.
-John
> Implement standard Serialization across Lucene versions
> -------------------------------------------------------
>
> Key: LUCENE-1473
> URL: https://issues.apache.org/jira/browse/LUCENE-1473
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Priority: Minor
> Attachments: LUCENE-1473.patch
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> To maintain serialization compatibility between Lucene versions,
> serialVersionUID needs to be added to classes that implement
> java.io.Serializable. java.io.Externalizable may be implemented in classes
> for faster performance.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
