[
https://issues.apache.org/jira/browse/HIVE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190195#comment-13190195
]
Ashutosh Chauhan commented on HIVE-2542:
----------------------------------------
On the second thought, HiveMetaHook is defined per table and not on per db
basis. So in dropDatabase() there is no hook to get. Different tables in a db
will have different hooks. Approach you have make sense in current design. Can
you create a phabricator review request for your patch. I will take a look.
> DROP DATABASE CASCADE does not drop non-native tables.
> -------------------------------------------------------
>
> Key: HIVE-2542
> URL: https://issues.apache.org/jira/browse/HIVE-2542
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Vandana Ayyalasomayajula
> Assignee: Vandana Ayyalasomayajula
> Labels: handler, hive, metastore, storage
> Attachments: Hive-2542.patch
>
>
> The hive meta store client does not delete the non-native tables during the
> drop database <dbname> cascade operation. As a result even though the
> database is deleted the tables still exist. This is related to HCATALOG-144.
> A deeper look at the HiveMetaStoreClient's "dropDatabase" function, tells us
> that the function does not utilize the hive meta hooks of the tables in the
> database for dropping the non-native tables.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
