[
https://issues.apache.org/jira/browse/FLINK-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther updated FLINK-12251:
---------------------------------
Description:
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#
was:
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.
> 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
> Assignee: Timo Walther
> Priority: Major
>
> 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
(v7.6.3#76005)
