[
https://issues.apache.org/jira/browse/HIVE-13778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303380#comment-15303380
]
Aaron Fabbri edited comment on HIVE-13778 at 5/27/16 3:01 AM:
--------------------------------------------------------------
Note this is the same as
[IMPALA-3558|https://issues.cloudera.org/projects/IMPALA/issues/IMPALA-3558].
See that issue for my explanation that this is expected behavior.
was (Author: fabbri):
Note this is the same as
[IMPALA-3558|https://issues.cloudera.org/projects/IMPALA/issues/IMPALA-3558]
> DROP TABLE PURGE on S3A table with too many files does not delete the files
> ---------------------------------------------------------------------------
>
> Key: HIVE-13778
> URL: https://issues.apache.org/jira/browse/HIVE-13778
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Sailesh Mukil
> Priority: Critical
> Labels: metastore, s3
>
> I've noticed that when we do a DROP TABLE tablename PURGE on a table on S3A
> that has many files, the files never get deleted. However, the Hive metastore
> logs do say that the path was deleted:
> "Not moving [path] to trash"
> "Deleted the diretory [path]"
> I initially thought that this was due to the eventually consistent nature of
> S3 for deletes, however, a week later, the files still exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
