hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.P Feng (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-18324) drop database failed for not empty tables, but acid table info in metastore is still deleted
Date Mon, 25 Dec 2017 02:22:02 GMT

    [ https://issues.apache.org/jira/browse/HIVE-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303019#comment-16303019
] 

J.P Feng edited comment on HIVE-18324 at 12/25/17 2:22 AM:
-----------------------------------------------------------

I think it also need to check event status in onDropTable and onDropPartition of AcidEventListener
before actually dropping table and dropping partition.


was (Author: snodawn):
I think it should also check event status in onDropTable and onDropPartition of AcidEventListener
before actually dropping table and dropping partition.

> 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)

Mime
View raw message