[
https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239614#comment-17239614
]
Kevin Kwon commented on FLINK-20368:
------------------------------------
[~danny0405] thanks for the information
how is this operator name generated? is it based on the table name?
will be even better if you drop me to the code base
> 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)
