[
https://issues.apache.org/jira/browse/AVRO-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kramer updated AVRO-3172:
------------------------------
Description:
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
was:
In Java, when migrating 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.
This issue was very annoying to isolate(from a big avro schema).
Even if this isn't strictly speaking a bug at least a warning should be issued
indicating issues might arise from the record name change.
I could replicate this using a simple test case on all versions of avro from
1.8.0 to 1.10.2
> 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)
