[
https://issues.apache.org/jira/browse/FLINK-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12304:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> AvroInputFormat should support schema evolution
> -----------------------------------------------
>
> Key: FLINK-12304
> URL: https://issues.apache.org/jira/browse/FLINK-12304
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.8.0
> Reporter: John
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> From the avro spec:
> _A reader of Avro data, whether from an RPC or a file, can always parse that
> data because its schema is provided. But that schema may not be exactly the
> schema that was expected. For example, if the data was written with a
> different version of the software than it is read, then records may have had
> fields added or removed._
> The AvroInputFormat should allow the application to supply a reader's schema
> to support cases where data was written with an old version of a schema and
> needs to be read with a newer version. The reader's schema can have addition
> fields with defaults so that the old schema can be adapted to the new. The
> underlying avro java library supports schema resolution, so adding support in
> AvroInputFormat should be straight forward.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
