You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/08/11 06:55:00 UTC

[jira] [Closed] (FLINK-32772) Add support of SET statements in the SQL Runner example

     [ https://issues.apache.org/jira/browse/FLINK-32772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-32772.
------------------------------
    Fix Version/s: kubernetes-operator-1.7.0
         Assignee: Mehdi
       Resolution: Fixed

merged to main a12b9431ac05965041d4c90d95592a40c3360692

> Add support of SET statements in the SQL Runner example
> -------------------------------------------------------
>
>                 Key: FLINK-32772
>                 URL: https://issues.apache.org/jira/browse/FLINK-32772
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.5.0
>            Reporter: Mehdi
>            Assignee: Mehdi
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.7.0
>
>
> When having a script containing `SET` statement the SQL Runner example execute it as an SQL query and is not setting the environment config instead.
> h2. How to reproduce
> This issue can be reproduced as follows:
>  * Add {{SET 'parallelism.default' = '2';}} on top of the SQL statements in [https://github.com/apache/flink-kubernetes-operator/blob/main/examples/flink-sql-runner-example/sql-scripts/statement-set.sql]
>  * Build and execute the example, and verify that the error {{The main method caused an error: Unsupported SQL query! executeSql() only accepts a single SQL statement of type [...]}} is happening in the pod log



--
This message was sent by Atlassian Jira
(v8.20.10#820010)