[
https://issues.apache.org/jira/browse/HIVE-14181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851538#comment-15851538
]
Adam Szita commented on HIVE-14181:
-----------------------------------
It is actually the issue in this ticket that if Hive fails to remove data from
disk, the Exception is swallowed and success is reported after drop table
command execution. (This then leaves data on the disk, but removes the Table
from HMS)
After my first patch a lot of tests have failed (600+) because of this - a lot
of them used to swallow errors that now got to the surface. Nevertheless I
added a new Conf key so that this stricter drop_table approach can be switched
off/on (default being off). This is now reflected in my 2nd patch
([^HIVE-14181.2.patch])
> 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.3.15#6346)
