[
https://issues.apache.org/jira/browse/FLINK-25337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460499#comment-17460499
]
Wenlong Lyu commented on FLINK-25337:
-------------------------------------
hi, [~vim-wang], I think it is because we need to check not only the table is
existed, but also the schema should be matched and query is valid, etc, it may
be better to put all check together.
Do you have any actual problem on the check? IMO, the failure check will soon
come up after convertSqlInsert. If you could post your case, others in
community could understand your problem better.
> Check whether the target table is valid when
> SqlToOperationConverter.convertSqlInsert
> -------------------------------------------------------------------------------------
>
> Key: FLINK-25337
> URL: https://issues.apache.org/jira/browse/FLINK-25337
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.14.0
> Reporter: vim-wang
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> when I execute insert sql like "insert into t1 select ...",
> If the t1 is not defined，sql will not throw an exception after
> SqlToOperationConverter.convertSqlInsert(), I think this is unreasonable, why
> not use catalogManager to check whether the target table is valid?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
