[
https://issues.apache.org/jira/browse/HIVE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719291#comment-16719291
]
Alan Gates commented on HIVE-21034:
-----------------------------------
It's not clear to me in an ephemeral cloud workload why you'd need this.
Either it attaches to an existing HMS, in which case you don't want to drop all
the databases, or it connects to an ephemeral HMS which will be dropped as part
of dropping the HMS in the cloud. Is there a case I'm missing?
I'm assuming there's no need to clean up the cloud datastore before returning
it to the cloud provider as they'll clean it. But if I'm wrong (or if for
security reasons users don't want to return it to the provider uncleaned) then
is the tool you're really looking for one that cleans out the entire metastore
schema? An inverse of --initSchema.
> 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
>
> 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)
