[
https://issues.apache.org/jira/browse/FLINK-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336684#comment-17336684
]
Flink Jira Bot commented on FLINK-8183:
---------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Add native Avro type support to the Table API & SQL
> ---------------------------------------------------
>
> Key: FLINK-8183
> URL: https://issues.apache.org/jira/browse/FLINK-8183
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Ecosystem
> Reporter: Timo Walther
> Priority: Major
> Labels: stale-major
>
> Avro types can pass the Table API, however, there should be a more native
> support in order to have the best user experience. This issue is an umbrella
> issue for tasks that would improve the handling of Avro types:
> Improvements could be:
> - Create a Avro type information that is created from an Avro schema that
> maps to all supported Table API types (full knowledge about key and values of
> lists, maps, and union types instead of {{GenericType}})
> - Convert {{Utf8}} (even in nested Avro types) to string when entering the
> Table API and convert it back if necessary
> - Add scalar functions to change certain values (e.g.,
> {{select('avroRecord.set("name", "Bob").set("age", 12))}}). This is in
> particular useful when a type has a lot of fields.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
