hive-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/HIVE-18705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545105#comment-16545105
] 

Hive QA commented on HIVE-18705:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12931756/HIVE-18705.11.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/12634/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12634/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12634/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12931756/HIVE-18705.11.patch
was found in seen patch url's cache and a test was probably run already on it. Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12931756 - PreCommit-HIVE-Build

> 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.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
(v7.6.3#76005)

Mime
View raw message