hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-18705) Improve HiveMetaStoreClient.dropDatabase
Date Mon, 16 Jul 2018 11:42:00 GMT


Hive QA commented on HIVE-18705:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14650 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12931756 - PreCommit-HIVE-Build

> Improve HiveMetaStoreClient.dropDatabase
> ----------------------------------------
>                 Key: HIVE-18705
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Adam Szita
>            Assignee: Adam Szita
>            Priority: Major
>         Attachments: HIVE-18705.0.patch, HIVE-18705.1.patch, HIVE-18705.10.patch, HIVE-18705.11.patch,
HIVE-18705.2.patch, HIVE-18705.4.patch, HIVE-18705.5.patch, HIVE-18705.6.patch, HIVE-18705.7.patch,
HIVE-18705.8.patch, HIVE-18705.9.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

View raw message