[
https://issues.apache.org/jira/browse/FLINK-27344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616698#comment-17616698
]
Alexey Leonov-Vendrovskiy commented on FLINK-27344:
---------------------------------------------------
Hi all,
+*System*+ stored procedures shouldn't be no more difficult to implement than
the any other new syntax.
You don't have to support user-defined stored procedures in order to make
system stored procedures to work. It can be thought as a way how the
functionality is manifested in the SQL FE (at parser level). The actual
implementation can stay exactly the same.
Some database systems choose this approach with system procedures/system
functions for modifying operations (which would be closer to the ANSI SQL):
BigQuery:
[https://cloud.google.com/bigquery/docs/reference/system-procedures#bqjobscancel]
Snowflake:
[https://docs.snowflake.com/en/sql-reference/functions/system_cancel_query.html]
While read-only operations can be accomplished via querying INFORMATION_SCHEMA
tables.
E.g. in BigQuery:
[https://cloud.google.com/bigquery/docs/information-schema-jobs]
Additional benefit of enabling read functionality as I_S is that it allows
users to specify additional filters to limit a subset of jobs they'd want to
see, or apply ordering etc. Of course it can be separately decided what query
features to support, but parser is already capable of translating the initial
query to an I_S table to a parsed form.
> 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)
