[
https://issues.apache.org/jira/browse/HIVE-14181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095257#comment-16095257
]
Adam Szita commented on HIVE-14181:
-----------------------------------
Hi [~daijy], we've taken a look on this [~aihuaxu] and [~vihangk1] a while back
but couldn't reach consensus. Please take a look on the RB link too.
I agree that rolling back (as the latest patch does) the HMS transaction is a
bad idea because the data deletion may fail partially, leaving an intact
metadata and corrupted data - that's a bad combo..
However I still think that we should at least throw the exception back to the
user to indicate that something went south while actually deleting the data,
and not just leave a warning in the log of HMS..
> DROP TABLE in hive doesn't Throw Error
> --------------------------------------
>
> Key: HIVE-14181
> URL: https://issues.apache.org/jira/browse/HIVE-14181
> Project: Hive
> Issue Type: Bug
> Environment: Hive 1.1.0
> CDH 5.5.1-1
> Reporter: Pranjal Singh
> Assignee: Adam Szita
> Labels: easyfix
> Attachments: HIVE-14181.1.patch, HIVE-14181.2.patch
>
>
> drop table table_name doen't throw an error if drop table fails.
> I was dropping a table and my trash didn't have enough space to hold the
> table but the drop table command showed success and the table wasn't deleted.
> But the hadoop fs -rm -r /hive/xyz.db/table_name/ gave an error "Failed to
> move to trash" because I didnot have enough space quota in my trash.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
