[
https://issues.apache.org/jira/browse/HIVE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015730#comment-13015730
]
Carl Steinbach commented on HIVE-2090:
--------------------------------------
Is the purpose of this ticket to make "DROP DATABASE x FORCE" behave like the
ANSI version of "DROP DATABASE x", e.g. delete x along with any tables in x? As
I recall the reason that DROP DATABASE does not currently adhere to ANSI
semantics is that we were worried about providing in the absence of a working
authorization system. Now that the authorization system exists, it seems like
"DROP DATABASE x FORCE" should be the default behavior, and the current
behavior should be something that you can enable via a configuration parameter,
e.g. hive.exec.drop.ignorenonempty=false.
Also, I the change to DDLTask.dropDatabase() introduces concurrency problems
since you're not operating in a transaction.
> Add "DROP DATABASE ... FORCE"
> -----------------------------
>
> Key: HIVE-2090
> URL: https://issues.apache.org/jira/browse/HIVE-2090
> Project: Hive
> Issue Type: New Feature
> Reporter: Siying Dong
> Assignee: Siying Dong
> Priority: Minor
> Attachments: HIVE-2090.1.patch
>
>
> A "DROP DATABASE ... FORCE" will be useful, when we use a database for
> isolation when doing some tests. Being able to force cleaning up the database
> will make test cleaning up easier.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
