[jira] [Commented] (FLINK-15392) SqlClient throws exception 'Table already exists' when repeated submit a same query

["liupengcheng (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003213#comment-17003213 ] 

liupengcheng commented on FLINK-15392:
--------------------------------------

I will try to create an PR for it later.

> SqlClient throws exception 'Table already exists' when repeated submit a same query
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-15392
>                 URL: https://issues.apache.org/jira/browse/FLINK-15392
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Client
>    Affects Versions: 1.10.0
>            Reporter: liupengcheng
>            Priority: Major
>
> When I was testing tpcds quries with sqlClient, but it reported the following failure when one query was submitted repeatedly.
> {code:java}
> [ERROR] Could not execute SQL statement. Reason:
> org.apache.flink.table.api.ValidationException: Table 'default: WITH customer_total_return AS
> ( SELECT
>     sr_customer_sk AS ctr_customer_sk,
>     sr_store_sk AS ctr_store_sk,
>     sum(sr_return_amt) AS ctr_total_return
>   FROM store_returns, date_dim
>   WHERE sr_returned_date_sk = d_date_sk AND d_year = 2000
>   GROUP BY sr_customer_sk, sr_store_sk)
> SELECT c_customer_id
> FROM customer_total_return ctr1, store, customer
> WHERE ctr1.ctr_total_return >
>   (SELECT avg(ctr_total_return) * 1.2
>   FROM customer_total_return ctr2
>   WHERE ctr1.ctr_store_sk = ctr2.ctr_store_sk)
>   AND s_store_sk = ctr1.ctr_store_sk
>   AND s_state = 'TN'
>   AND ctr1.ctr_customer_sk = c_customer_sk
> ORDER BY c_customer_id
> LIMIT 100' already exists. Please choose a different name.{code}
> I checked the code, it seems that it will always create a new table and registerTableSink, and caused the failure.
> I think we can do some work here to fix it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)