You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Daniel Voros (JIRA)" <ji...@apache.org> on 2019/03/01 10:57:00 UTC
[jira] [Commented] (HIVE-21034) Add option to schematool to drop
Hive databases
[ https://issues.apache.org/jira/browse/HIVE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781572#comment-16781572 ]
Daniel Voros commented on HIVE-21034:
-------------------------------------
Attached patch #3 that is rebased on master (classes moved in HIVE-21298) and also moves the "yes" handling to the task as suggested by Miklos.
[~mgergely] I've seen NPEs there when {{MetastoreSchemaTool#init()}} failed before (or during) setting cmdLine, that's why I've added the null-check.
[~ashutoshc], [~alangates] could you please also take a look?
> Add option to schematool to drop Hive databases
> -----------------------------------------------
>
> Key: HIVE-21034
> URL: https://issues.apache.org/jira/browse/HIVE-21034
> Project: Hive
> Issue Type: Improvement
> Reporter: Daniel Voros
> Assignee: Daniel Voros
> Priority: Major
> Attachments: HIVE-21034.1.patch, HIVE-21034.2.patch, HIVE-21034.2.patch, HIVE-21034.3.patch
>
>
> An option to remove all Hive managed data could be a useful addition to {{schematool}}.
> I propose to introduce a new flag {{-dropAllDatabases}} that would *drop all databases with CASCADE* to remove all data of managed tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)