You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/09/13 13:26:00 UTC
[jira] [Commented] (AVRO-3172) Alias break when writer schema and
reader schema name differs
[ https://issues.apache.org/jira/browse/AVRO-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414196#comment-17414196 ]
ASF subversion and git services commented on AVRO-3172:
-------------------------------------------------------
Commit b6491f3f9d196867f52393985d849af54f245fbd in avro's branch refs/heads/master from Martin Tzvetanov Grigorov
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=b6491f3 ]
AVRO-3172 Since there is no read on the Readable there is no 'end' event
Calling writeable.end() emits 'finish' event
> Alias break when writer schema and reader schema name differs
> -------------------------------------------------------------
>
> Key: AVRO-3172
> URL: https://issues.apache.org/jira/browse/AVRO-3172
> Project: Apache Avro
> Issue Type: Bug
> Reporter: Ilya Kramer
> Priority: Major
>
> In Java, when migrating a field from one name to another via alias (for example in _schema.old_ a field was named _a_, in _schema.new_ the field is renamed to _b_ with alias to _a_) the alias is not considered if the record name in _schema.old_ differs from the one in _schema.new_.
> This is especially painful as nothing else breaks and there's no warning issued about the change of the record name causing potential problems.
> This issue was very annoying to isolate(from a big avro schema).
> I could replicate this using a simple test case on all versions of avro from 1.8.0 to 1.10.2
--
This message was sent by Atlassian Jira
(v8.3.4#803005)