[
https://issues.apache.org/jira/browse/FLINK-27344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614320#comment-17614320
]
Paul Lin commented on FLINK-27344:
----------------------------------
[~ekoblov] Yes, we've roughly considered the stored procedures approach, but
given that Flink currently doesn't support stored procedures and it's not very
straightforward from the users' point of view, we then lean toward the new
syntax approach (as many databases also provide similar SQL statements to
control jobs/tasks, like Hive/CrukroachDB/KSQL). WDYT?
> FLIP-222: Support full job lifecycle statements in SQL client
> -------------------------------------------------------------
>
> Key: FLINK-27344
> URL: https://issues.apache.org/jira/browse/FLINK-27344
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Client
> Reporter: Paul Lin
> Assignee: Paul Lin
> Priority: Major
>
> With the efforts in FLIP-24 and FLIP-91, Flink SQL client supports submitting
> SQL jobs but lacks further support for their lifecycles afterward which is
> crucial for streaming use cases. That means Flink SQL client users have to
> turn to other clients (e.g. CLI) or APIs (e.g. REST API) to manage the jobs,
> like triggering savepoints or canceling queries, which makes the user
> experience of SQL client incomplete.
> Therefore, this proposal aims to complete the capability of SQL client by
> adding job lifecycle statements. With these statements, users could manage
> jobs and savepoints through pure SQL in SQL client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
