[ 
https://issues.apache.org/jira/browse/FLINK-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-12251:
-----------------------------------
      Labels: auto-deprioritized-major auto-unassigned  (was: auto-unassigned 
stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 days 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.


> Rework the Table API & SQL type system
> --------------------------------------
>
>                 Key: FLINK-12251
>                 URL: https://issues.apache.org/jira/browse/FLINK-12251
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> Currently, the Table & SQL API relies on Flink’s TypeInformation at different 
> positions in the code base. The API uses it for conversion between 
> DataSet/DataStream API, casting, and table schema representation. The 
> planning for code generation and serialization of runtime operators.
> The past has shown that TypeInformation is useful when converting between 
> DataSet/DataStream API, however, it does not integrate nicely with SQLs type 
> system and depends on the programming language that is used.
> There is consensus to perform a big rework of the type system with a better 
> long-term vision and closer semantics to other SQL vendors and the standard 
> itself.
> FLIP-37 discusses the mid-term and long-term plan for supported types and 
> their semantics.
> https://docs.google.com/document/d/1a9HUb6OaBIoj9IRfbILcMFPrOL7ALeZ3rVI66dvA2_U/edit#



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to