[
https://issues.apache.org/jira/browse/FLINK-25171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shouzuo meng updated FLINK-25171:
---------------------------------
Description:
When I execute the DDL statement, I mistakenly use the duplicate field name in
THE SQL, but the execution result of the program does not throw any exception
or prompt. In MergeTableLikeUtilTest. Java# mergePhysicalColumns add repeated
the TableColumn (), also do not throw any exceptions, review the code logic
found only on the source table schema fields, It is not a duplicate and derived
tables and fields of the source table is verified, and no field of derived
tables if repeated verification, adding physicalFieldNamesToTypes, there will
be a repeating field coverage,The following are the execution statements and
the results
DDL sql：
CREATE TABLE test1 (
`log_version` string COMMENT '日志版本',
`log_version` INTEGER COMMENT '日志版本',
`pv_time` string COMMENT '日志时间'
) with(
'connector' = 'kafka',
'topic' = 'xxx',
'properties.bootstrap.servers' = 'xxx:9110',
'scan.startup.mode'='latest-offset',
'format' = 'json',
)
was:
When I execute the DDL statement, I mistakenly use the duplicate field name in
THE SQL, but the execution result of the program does not throw any exception
or prompt. In MergeTableLikeUtilTest. Java# mergePhysicalColumns add repeated
the TableColumn (), also do not throw any exceptions, review the code logic
found only on the source table schema fields, It is not a duplicate and derived
tables and fields of the source table is verified, and no field of derived
tables if repeated verification, adding physicalFieldNamesToTypes, there will
be a repeating field coverage
DDL sql：
CREATE TABLE test1 (
`log_version` string COMMENT '日志版本',
`log_version` INTEGER COMMENT '日志版本',
`pv_time` string COMMENT '日志时间'
) with(
'connector' = 'kafka',
'topic' = 'xxx',
'properties.bootstrap.servers' = 'xxx:9110',
'scan.startup.mode'='latest-offset',
'format' = 'json',
)
> When the DDL statement was executed, the column names of the Derived Columns
> were not validated
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-25171
> URL: https://issues.apache.org/jira/browse/FLINK-25171
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.14.0
> Reporter: shouzuo meng
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: 5251638775474_.pic.jpg
>
>
> When I execute the DDL statement, I mistakenly use the duplicate field name
> in THE SQL, but the execution result of the program does not throw any
> exception or prompt. In MergeTableLikeUtilTest. Java# mergePhysicalColumns
> add repeated the TableColumn (), also do not throw any exceptions, review the
> code logic found only on the source table schema fields, It is not a
> duplicate and derived tables and fields of the source table is verified, and
> no field of derived tables if repeated verification, adding
> physicalFieldNamesToTypes, there will be a repeating field coverage,The
> following are the execution statements and the results
> DDL sql：
> CREATE TABLE test1 (
> `log_version` string COMMENT '日志版本',
> `log_version` INTEGER COMMENT '日志版本',
> `pv_time` string COMMENT '日志时间'
> ) with(
> 'connector' = 'kafka',
> 'topic' = 'xxx',
> 'properties.bootstrap.servers' = 'xxx:9110',
> 'scan.startup.mode'='latest-offset',
> 'format' = 'json',
> )
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
