[
https://issues.apache.org/jira/browse/FLINK-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334405#comment-17334405
]
Jark Wu commented on FLINK-22318:
---------------------------------
[~todd5167]
1. The {{SqlValidatorException}} may be not because of non-existent fields,
maybe invalid expression/udfs, etc... If we want to throw an accurate
exception, a better solution can be using
{{org.apache.flink.table.catalog.DefaultSchemaResolver#resolve}} to resolve a
{{Schema}}, and then you should be able to traverse the resolved expression
tree to see whether it contains renamed column.
2. I'm fine with this.
Besides, we can continue the disucssion in PR, don't need to swtich between
JIRA and PR.
> Support RENAME column name for ALTER TABLE statement
> ----------------------------------------------------
>
> Key: FLINK-22318
> URL: https://issues.apache.org/jira/browse/FLINK-22318
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Jark Wu
> Priority: Major
> Labels: pull-request-available
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
