[
https://issues.apache.org/jira/browse/FLINK-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15718737#comment-15718737
]
Dave Torok commented on FLINK-5039:
-----------------------------------
I have spent 2 days on this and HAVE THE SOLUTION.
Fix: Bump Avro version to at least 1.7.7 from the current 1.7.6.
Root Cause. Within "Schema.class" the "field" position is a TRANSIENT and does
not get serialized by Kryo!
See https://issues.apache.org/jira/browse/AVRO-1476 and specififcally mentions
kyro
This was fixed in 1.7.7
This is also the cause for other GenericRecord issues such as the 'union' issue
mentioned here
http://stackoverflow.com/questions/37115618/apache-flink-union-operator-giving-wrong-response
PLEASE BUMP THIS ASAP!!!!
I have verified the fix in my local machine by replacing the Avro classes
within the flink-dist_2.11-1.1.3.jar and it corrected my issue.
> Avro GenericRecord support is broken
> ------------------------------------
>
> Key: FLINK-5039
> URL: https://issues.apache.org/jira/browse/FLINK-5039
> Project: Flink
> Issue Type: Bug
> Components: Batch Connectors and Input/Output Formats
> Affects Versions: 1.1.3
> Reporter: Bruno Dumon
> Priority: Minor
>
> Avro GenericRecord support was introduced in FLINK-3691, but it seems like
> the GenericRecords are not properly (de)serialized.
> This can be easily seen with a program like this:
> {noformat}
> env.createInput(new AvroInputFormat<>(new Path("somefile.avro"),
> GenericRecord.class))
> .first(10)
> .print();
> {noformat}
> which will print records in which all fields have the same value:
> {noformat}
> {"foo": 1478628723066, "bar": 1478628723066, "baz": 1478628723066, ...}
> {"foo": 1478628723179, "bar": 1478628723179, "baz": 1478628723179, ...}
> {noformat}
> If I'm not mistaken, the AvroInputFormat does essentially
> TypeExtractor.getForClass(GenericRecord.class), but GenericRecords are not
> POJOs.
> Furthermore, each GenericRecord contains a pointer to the record schema. I
> guess the current naive approach will serialize this schema with each record,
> which is quite inefficient (the schema is typically more complex and much
> larger than the data). We probably need a TypeInformation and TypeSerializer
> specific to Avro GenericRecords, which could just use avro serialization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
