[ 
https://issues.apache.org/jira/browse/FLINK-8716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328660#comment-17328660
 ] 

Flink Jira Bot commented on FLINK-8716:
---------------------------------------

This major issue is unassigned and itself and all of its Sub-Tasks have not 
been updated for 30 days. So, it has been labeled "stale-major". If this ticket 
is indeed "major", please either assign yourself or give an update. Afterwards, 
please remove the label. In 7 days the issue will be deprioritized.

> AvroSerializer does not use schema of snapshot
> ----------------------------------------------
>
>                 Key: FLINK-8716
>                 URL: https://issues.apache.org/jira/browse/FLINK-8716
>             Project: Flink
>          Issue Type: Bug
>          Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
>    Affects Versions: 1.4.0
>            Reporter: Arvid Heise
>            Priority: Major
>              Labels: stale-major
>
> The new AvroSerializer stores the schema in the snapshot and uses it to 
> validate compability.
> However, it does not use the schema of the snapshot while reading the data. 
> This version will fail for any change of the data layout (so it supports more 
> or less only renaming currently).
>  
> [https://github.com/apache/flink/blob/f3a2197a23524048200ae2b4712d6ed833208124/flink-formats/flink-avro/src/main/java/org/apache/flink/formats/avro/typeutils/AvroSerializer.java#L265]
>  needs to use the schema from
>  
> [https://github.com/apache/flink/blob/f3a2197a23524048200ae2b4712d6ed833208124/flink-formats/flink-avro/src/main/java/org/apache/flink/formats/avro/typeutils/AvroSerializer.java#L188]
>  as the first parameter. Accordingly, a readSchema field need to be set
>  in #ensureCompatibility and relayed in #duplicate. Note that the readSchema 
> is passed as the write schema parameter to the DatumReader, as it was the 
> schema that was used to write the data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to