You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2019/11/19 11:23:00 UTC
[jira] [Commented] (FLINK-14764) The final Explicit/Implicit
conversion matrix we should support in our planner
[ https://issues.apache.org/jira/browse/FLINK-14764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977403#comment-16977403 ]
Timo Walther commented on FLINK-14764:
--------------------------------------
We recently added {{org.apache.flink.table.types.logical.utils.LogicalTypeCasts}} and corresponding tests that should serve as the reference implementation for what we should support in the near future.
> The final Explicit/Implicit conversion matrix we should support in our planner
> ------------------------------------------------------------------------------
>
> Key: FLINK-14764
> URL: https://issues.apache.org/jira/browse/FLINK-14764
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Legacy Planner, Table SQL / Planner
> Affects Versions: 1.10.0
> Reporter: Zhenghua Gao
> Priority: Blocker
> Fix For: 1.10.0
>
> Attachments: SQL_2011_CAST_Matrix.png
>
>
> The SQL standard defines the cast specification with an explicit conversion matrix (SQL 2011 Part 2 Section 6.13 Syntax Rules 6)). But neither Legacy planner nor blink planner would follow that. IMO we should determine a final Explicit/Implicit conversion matrix before 1.10 (at least in blink planner).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)