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

Sean Mackrory edited comment on HADOOP-13998 at 6/2/17 7:23 PM:
----------------------------------------------------------------

[[email protected]] - regarding that test issue, that would happen if a 
directory was deleted and a file inside it was then created without correctly 
overwriting or removing the tombstone of the parent directories. If you're 
using the DynamoDB implementation, it should definitely be replacing the 
tombstone for the parent directory when the file is created. If you're using 
the Local implementation, I wonder if that's happening as a result of 
HADOOP-14457. I'll take a closer look at that again and see if I can reproduce, 
though I thought I had added test cases for that sequence.


was (Author: mackrorysd):
[[email protected]] - regarding that test issue, that would happen if a 
directory was deleted, and a file inside it was then created. If you're using 
the DynamoDB implementation, it should definitely be replacing the tombstone 
for the parent directory when the file is created. If you're using the Local 
implementation, I wonder if that's happening as a result of HADOOP-14457. I'll 
take a closer look at that again and see if I can reproduce, though I thought I 
had added test cases for that sequence.

> initial s3guard preview
> -----------------------
>
>                 Key: HADOOP-13998
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13998
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Steve Loughran
>
> JIRA to link in all the things we think are needed for a preview/merge into 
> trunk



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to