[
https://issues.apache.org/jira/browse/FLINK-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353337#comment-17353337
]
Rui Li commented on FLINK-22272:
--------------------------------
These are actually two different problems:
# Whether we allow "DROP TABLE" to drop views, or "DROP VIEW" to drop tables
# If HiveCatalog allows creating generic tables with empty schema, whether it
should also allow retrieving such tables. This has nothing to do with DROP TABLE
For #1, I think we should continue guard against such scenarios. That means we
can't revert FLINK-17756.
For #2, I think the current behavior in HiveCatalog is inconsistent and it
should support retrieving generic tables with empty schema.
> 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)
