[
https://issues.apache.org/jira/browse/HIVE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719253#comment-16719253
]
Daniel Voros commented on HIVE-21034:
-------------------------------------
Thank you for the feedback. I do agree with you, it's a dangerous operation,
and we should make sure it's hard do accidentally/maliciously invoke. I was
hoping to find some documentation on how to secure your deployment with respect
to restricting access to schematool and other executables, but came back empty
handed so I'm not sure what (if any) protections we already have (or suggest to
have) in place.
What I had in mind for use-cases was ephemeral cloud workloads, where the users
might want to drop everything once the job has finished.
> 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)
