[
https://issues.apache.org/jira/browse/FLINK-37064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruan Hang updated FLINK-37064:
------------------------------
Fix Version/s: 2.3.0
(was: 2.2.0)
> 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
> Affects Versions: 2.1.0
> Reporter: Feng Jin
> Priority: Major
> Fix For: 2.3.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)
