[
https://issues.apache.org/jira/browse/LUCENE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653413#action_12653413
]
Doug Cutting commented on LUCENE-1473:
--------------------------------------
> 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.
But VM1 might require an older field that the new field replaced, and VM1 may
then crash in an unpredictable way. Not defining explicit suid's is more
conservative: you get a well-defined exception when things might not work.
Defining suid's but doing nothing else about compatibility is playing
fast-and-loose: it might work in many cases, but it also might cause strange,
hard-to-diagnose problems in others. If we want Lucene to work reliably across
versions, then we need to commit to that goal as a project, define the limits
of the compatibility, implement Externalizeable, add tests, etc. Just adding
suid's doesn't achieve that, so far as I can see.
> 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]
