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

Posted to issues@flink.apache.org by "Feng Jin (Jira)" <ji...@apache.org> on 2025/01/08 10:44:00 UTC

[jira] [Created] (FLINK-37064) Validate Schema Column Name Conflicts in Definition Query During Materialized Table Creation or Alter Query

Feng Jin created FLINK-37064:
--------------------------------

             Summary: Validate Schema Column Name Conflicts in Definition Query During Materialized Table Creation or Alter Query
                 Key: FLINK-37064
                 URL: https://issues.apache.org/jira/browse/FLINK-37064
             Project: Flink
          Issue Type: Improvement
          Components: Table SQL / Gateway
            Reporter: Feng Jin
             Fix For: 2.0.0


By default, when duplicate field names appear in the definition query, Calcite automatically appends an index to the field names to prevent conflicts. However, when generating a schema based on the query, we should explicitly check for and handle field name conflicts instead of relying on Calcite’s default behavior. This ensures that the resulting schema is consistent with user expectations and avoids unintended naming patterns.



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