[
https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327510#comment-17327510
]
Flink Jira Bot commented on FLINK-20368:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> 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
> Labels: stale-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)
