[
https://issues.apache.org/jira/browse/FLINK-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068217#comment-17068217
]
godfrey he commented on FLINK-16709:
------------------------------------
Hi [~zhangjun], Thanks for the suggestion. the drawback of {{set
execution.job-name = jobname'}} is users must call such command for each
statement, otherwise all job names are same.
I think it's better sql client can extract some info from a statement , we can
use such simple info as the job name, instead of the whole sql statement. One
approach is extracting source table names for {{SELECT}} statement and
extracting sink table names for {{INSERT}} statement.
e.g.
"select xx from MyTable ..." -- job name is {{session_id:select_MyTable}}
"insert into MySink select xx from MyTable ..." -- job name is
{{session_id:insert_MySink}}
> add a set command to set job name when submit job on sql client
> ---------------------------------------------------------------
>
> Key: FLINK-16709
> URL: https://issues.apache.org/jira/browse/FLINK-16709
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Client
> Affects Versions: 1.10.0
> Reporter: Jun Zhang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we submit a sql job in the sql client, the default job name is sessionid
> + sql, and the job name cannot be specified, but when the sql is very long,
> for example, I have 100 columns, this will be unfriendly to display on the
> web UI ,when there are many jobs, it is not easy to find job. So we add a
> command 'set execution.job-name = jobname' which can set the job name of the
> submitted job
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
