[
https://issues.apache.org/jira/browse/FLINK-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354199#comment-17354199
]
wangzeyu commented on FLINK-22272:
----------------------------------
Hi [Rui Li|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lirui],
i used to think move the feature to Catalog has a more direct way to know what
is the table attribute for TABLE/VIEW, and we can do everything in catalog
isself when drop table/view because the different catalog maybe need deal
different thing. But as you say Flink should provide consistent semantics for
DROP TABLE/VIEW no matter what Catalog is being used. So i will submit a new PR
for #2, could you help review?
> Some scenes can't drop table by hive catalog
> --------------------------------------------
>
> Key: FLINK-22272
> URL: https://issues.apache.org/jira/browse/FLINK-22272
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Hive
> Affects Versions: 1.12.1
> Reporter: wangzeyu
> Priority: Major
> Labels: pull-request-available, stale-major
> Fix For: 1.12.1
>
>
> There are some scenes we can't drop table by hive catalog because of we
> execute error create table sql like "caeate table tableName". And then when
> we execute drop table sql "drop table tableName" will throw error
> "org.apache.flink.table.catalog.exceptions.CatalogException: Failed to get
> table schema from properties for generic table".
> So, i think maybe we should remove the check when we drop table by
> third-party catalog and just drop table depend on the third-party catalog.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
