[
https://issues.apache.org/jira/browse/STORM-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123554#comment-15123554
]
ASF GitHub Bot commented on STORM-1504:
---------------------------------------
Github user dossett commented on the pull request:
https://github.com/apache/storm/pull/1052#issuecomment-176801519
Thanks everyone for the feedback on the code. I am beginning to appreciate
some of the challenges of serialization, in particular whatever serializer is
registered with kryo can only be invoked with a default constructor, so my
naive implementation, which relies on initializations via constructors in some
spots will not work. The meaning of @revans2's comments about reading data from
a special file in the jar are also becoming clearer to me -- that's a way to
get information needed for initialization without relying on constructor
parameters. I'll take another pass at cleaning up at least some of these
issues and fixing/addressing comments. There's some excitement here about
using our Confluent registry to speed up serialization, so I really want to
make this work.
These are some new corners of java for me, so in the worst case scenario
I'll simply have learned a lot. Thanks everyone!
> AvroGenericRecordBolt will not work in a topology with multiple workers
> -----------------------------------------------------------------------
>
> Key: STORM-1504
> URL: https://issues.apache.org/jira/browse/STORM-1504
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Aaron Dossett
> Assignee: Aaron Dossett
> Priority: Critical
>
> It receives Avro GenericRecord objects, which leads to serialization errors
> in a multi-worker topology. Specifically, GenericData.Record will throw a
> serialization error.
> A serializer for this class should be added and registered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
