[
https://issues.apache.org/jira/browse/AVRO-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-600:
------------------------------
Status: Patch Available (was: Open)
Hadoop Flags: [Incompatible change]
Fix Version/s: 1.4.0
I think this is ready to commit.
> add support for type and field name aliases
> -------------------------------------------
>
> Key: AVRO-600
> URL: https://issues.apache.org/jira/browse/AVRO-600
> Project: Avro
> Issue Type: New Feature
> Components: java, spec
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.4.0
>
> Attachments: AVRO-600.patch, AVRO-600.patch
>
>
> It would be good if Avro would permit one to still read data if a type or
> field name has been changed. I propose we add a notion of name _aliases_.
> Aliases could be listed for every named type and for record fields. The
> writers schema would be permitted to contain any of the aliases.
> In general, this permits one to construct schemas that can read different
> types into a single type. One could use this not just to handle renamings,
> but also to join different datasets. For example, if two datasets each
> contain differently named records with a date and an ip address field, this
> could be used be used to project these both to a single record with just
> those fields.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
