[
https://issues.apache.org/jira/browse/FLINK-27344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621418#comment-17621418
]
Alexey Leonov-Vendrovskiy commented on FLINK-27344:
---------------------------------------------------
I think it is fine to proceed with the current plan if things are already
decided and voted upon. The drawback could be is that it is could be more work
to introduce changes to grammar (maybe this is already solved?) and general
divergence from the standard, which is debatable.
I suggest at least to keep the idea of system stored procedures for the future
developments.
W.r.t. I_S I agree, it might require some changes in the design of catalogs,
so, looks like not now. The confusion could be resolved with the documentation
;).
> 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)
