You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2019/11/26 12:20:00 UTC

[jira] [Commented] (BEAM-8819) AvroCoder for SpecificRecords is not serialized correctly since 2.13.0

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

Maximilian Michels commented on BEAM-8819:
------------------------------------------

Marking Fix Version 2.17.0 because this looks important enough to fix for the release. Pull request is ready.

> AvroCoder for SpecificRecords is not serialized correctly since 2.13.0
> ----------------------------------------------------------------------
>
>                 Key: BEAM-8819
>                 URL: https://issues.apache.org/jira/browse/BEAM-8819
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>    Affects Versions: 2.13.0, 2.14.0, 2.15.0, 2.16.0
>            Reporter: Piotr Szczepanik
>            Assignee: Piotr Szczepanik
>            Priority: Major
>             Fix For: 2.17.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> While trying to upgrade our pipelines from Beam 2.11.0 to Beam 2.16.0 we found that our SpecificRecords used in PCollection were being decoded as GenericRecords.
> After some investigation we found the specific commit/issue that we think did brake it:
> [https://github.com/apache/beam/pull/8342/files]
> https://issues.apache.org/jira/browse/BEAM-7103
> After the mentioned change all AvroCoders are serialized as simple urn: "beam:coder:avro:v1" which means they are deserialized / rehydrated as AvroCoder<GenericRecord>.



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