[jira] [Commented] (HIVE-2542) DROP DATABASE CASCADE does not drop non-native tables.
[ https://issues.apache.org/jira/browse/HIVE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190245#comment-13190245 ] Vandana Ayyalasomayajula commented on HIVE-2542: Hey Carl, here is the link to the request: https://reviews.facebook.net/D1347 > 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 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
[jira] [Commented] (HIVE-2542) DROP DATABASE CASCADE does not drop non-native tables.
[ https://issues.apache.org/jira/browse/HIVE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190202#comment-13190202 ] Vandana Ayyalasomayajula commented on HIVE-2542: I have created a phabricator review request for the patch. > 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 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
[jira] [Commented] (HIVE-2542) DROP DATABASE CASCADE does not drop non-native tables.
[ https://issues.apache.org/jira/browse/HIVE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173616#comment-13173616 ] Vandana Ayyalasomayajula commented on HIVE-2542: Hey Ashutosh, I have been busy with some other project priorities. I will start working on this in the beginning of next year. > 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 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
