[
https://issues.apache.org/jira/browse/ATLAS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suma Shivaprasad updated ATLAS-529:
-----------------------------------
Attachment: ATLAS-529.2.patch
Rebased with trunk
> support drop database
> ---------------------
>
> Key: ATLAS-529
> URL: https://issues.apache.org/jira/browse/ATLAS-529
> Project: Atlas
> Issue Type: Sub-task
> Affects Versions: 0.7-incubating
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-529.1.patch, ATLAS-529.2.patch, ATLAS-529.patch
>
>
> Supports both
> a. Drop database [restrict] - default mode is restrict
> b. DROP database cascase
> Drop database restrict expects that the database is empty and does not have
> any valid hive tables present when it is called else it fails on hive itself
> and the hook is not called in this case
> In case of DROP database cascade , the hive server send information on the
> tables deleted and the database itself being deleted in the order mentioned .
> Hence drop database cascade generates a series of notification messages all
> expected to be executed in order to drop tables first and then the database
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
