[
https://issues.apache.org/jira/browse/AVRO-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905393#comment-15905393
]
Sean Busbey commented on AVRO-1502:
-----------------------------------
{quote}
Marking this as incompatible, as it changes the class hierarchy for
SpecificFixed. Updating the Avro library without recompiling the IPC classes
(in my test this was for Flume) results in an AbstractMethodError.
I'll add something to the release notes.
{quote}
I'm trying to make sure this gets documented enough in the description, since
we can't add a release note to a closed issue. [~tomwhite] do you happen to
have an easy way to generate an example stacktrace for the failure?
Looking at the changes related to this jira, I think the problem is that
{{SpecificFixed}} now expects the generated code to implement the
{{getSchema()}} method. Is that right? I think this means that anyone with
generated classes that embed a {{fixed}} type need to regenerate. Or maybe it's
just if the top level generated class is for a {{fixed}} type (and for example,
a {{record}} with a {{fixed}} field would be fine)? I just want to make sure I
call out the right thing in the note.
> Avro objects should implement Serializable
> ------------------------------------------
>
> Key: AVRO-1502
> URL: https://issues.apache.org/jira/browse/AVRO-1502
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Jeff Hammerbacher
> Assignee: Doug Cutting
> Fix For: 1.8.0
>
> Attachments: AVRO-1502.patch, AVRO-1502.patch,
> serializeable_base.patch
>
>
> To ease use of Avro objects with systems that rely on Java serialization,
> i.e. Apache Spark, this change updates generated classes to implement
> {{java.io.Externalizable}}.
> This change is marked incompatible because the class hierarchy for
> SpecificFixed has changed. Updating the Avro library without recompiling the
> IPC classes (in my test this was for Flume) results in an AbstractMethodError.
> (I couldn't add a Release Note since the jira is Closed, so I'm updating the
> description instead.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
