You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2017/12/21 16:33:01 UTC
[jira] [Updated] (HIVE-18324) drop database failed for not empty
tables, but acid table info in metastore is still deleted
[ https://issues.apache.org/jira/browse/HIVE-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eugene Koifman updated HIVE-18324:
----------------------------------
Component/s: Transactions
> drop database failed for not empty tables, but acid table info in metastore is still deleted
> ---------------------------------------------------------------------------------------------
>
> Key: HIVE-18324
> URL: https://issues.apache.org/jira/browse/HIVE-18324
> Project: Hive
> Issue Type: Bug
> Components: Hive, Transactions
> Affects Versions: 2.1.1, 2.3.2
> Reporter: J.P Feng
>
> I use "drop database hive_test" to drop database (without cascade) , because it's not empty, my operation runs fail, and throws exception -> InvalidOperationException(message:Database hive_test is not empty. One or more tables exist.)
> but acid tables info in TXN_COMPONENTS,COMPLETED_TXN_COMPONENTS,COMPACTION_QUEUE,COMPLETED_COMPACTIONS is still deleted by AcidEventListener.
> So I advise that, onDropDatabase in AcidEventListener need to judge DropDatabaseEvent.getStatus before delete acid table info.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)