hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Szita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-18705) Improve HiveMetaStoreClient.dropDatabase
Date Wed, 20 Jun 2018 11:31:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adam Szita updated HIVE-18705:
------------------------------
    Attachment: HIVE-18705.6.patch

> 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
>         Attachments: HIVE-18705.0.patch, HIVE-18705.1.patch, HIVE-18705.2.patch, HIVE-18705.4.patch,
HIVE-18705.5.patch, HIVE-18705.6.patch
>
>
> {{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)

Mime
View raw message