You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2025/12/10 21:09:00 UTC

[jira] [Created] (FLINK-38802) DDL with duplicated keys in table options should fail

Sergey Nuyanzin created FLINK-38802:
---------------------------------------

             Summary: DDL with duplicated keys in table options should fail
                 Key: FLINK-38802
                 URL: https://issues.apache.org/jira/browse/FLINK-38802
             Project: Flink
          Issue Type: Bug
          Components: Table SQL / Planner
            Reporter: Sergey Nuyanzin
            Assignee: Sergey Nuyanzin


Right now any DDL, for instance
{code:sql}
ALTER CATALOG cat SET ('K1' = 'V1', 'k2' = 'v2', 'k2' = 'another_value')
{code}
currently takes into account only the latest value for {{k2}} which happens silently. It is much better if it fails while validation to make it more transparent for the user



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