[ https://issues.apache.org/jira/browse/HIVE-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365962#comment-16365962 ]
Adam Szita commented on HIVE-18705: ----------------------------------- I guess it is because of client side hooks. I intend to rearrange the order things happen with the hooks so that all dropTable hooks run first and then we only send one dropDB to HMS server side. But before I upload any patches I also want to run some performance tests first to see how much speed-up we'd win. > Improve HiveMetaStoreClient.dropDatabase > ---------------------------------------- > > Key: HIVE-18705 > URL: https://issues.apache.org/jira/browse/HIVE-18705 > Project: Hive > Issue Type: Improvement > Reporter: Adam Szita > Assignee: Adam Szita > Priority: Major > > {{HiveMetaStoreClient.dropDatabase}} has a strange implementation to ensure > dealing with client side hooks (for non-native tables e.g. HBase). Currently > it starts by retrieving all the tables from HMS, and then sends {{dropTable}} > calls to HMS table-by-table. At the end a {{dropDatabase}} just to be sure :) > I believe this could be refactored so that it speeds up the dropDB in > situations where the average table count per DB is very high. -- This message was sent by Atlassian JIRA (v7.6.3#76005)