[
https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239503#comment-17239503
]
Danny Chen commented on FLINK-20368:
------------------------------------
Hi [~ksp0422] ~
The DDL does not use DataStream API, for Blink planner, not of the operator
codes are code-gened and chained through {{Transformation}}s, the operator name
strategy is kind of builtin and user never see it.
> Will it break like normal SELECT queries when upgrading
If we keep operator name unchanged, it expected to be compatible.
> Supports custom operator name for Flink SQL
> -------------------------------------------
>
> Key: FLINK-20368
> URL: https://issues.apache.org/jira/browse/FLINK-20368
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 1.12.0
> Reporter: Danny Chen
> Priority: Major
>
> A request from USER mailing list from Kevin Kwon:
> For SQLs, I know that the operator ID assignment is not possible now since
> the query optimizer may not be backward compatible in each release
> But are DDLs also affected by this?
> for example,
> CREATE TABLE mytable (
> id BIGINT,
> data STRING
> ) with (
> connector = 'kafka'
> ...
> id = 'mytable'
> name = 'mytable'
> )
> and we can save all related checkpoint data
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
