You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sailesh Mukil (JIRA)" <ji...@apache.org> on 2016/05/18 18:18:12 UTC
[jira] [Comment Edited] (HIVE-13778) DROP TABLE PURGE on S3A table
with too many files does not delete the files
[ https://issues.apache.org/jira/browse/HIVE-13778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289504#comment-15289504 ]
Sailesh Mukil edited comment on HIVE-13778 at 5/18/16 6:18 PM:
---------------------------------------------------------------
[~ashutoshc] I noticed that this happens usually around 25+ files.
was (Author: sailesh):
I noticed that this happens usually around 25+ files.
> 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)