You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2017/04/20 22:27:04 UTC

[jira] [Commented] (HADOOP-13760) S3Guard: add delete tracking

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

Sean Mackrory commented on HADOOP-13760:
----------------------------------------

Also, this is a schema change but the .001. patch doesn't update the version yet. I'm going to start looking at how to move from one schema version to the next, because I'm realizing we don't have an ideal way to deal with that yet. 

> S3Guard: add delete tracking
> ----------------------------
>
>                 Key: HADOOP-13760
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13760
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Aaron Fabbri
>            Assignee: Sean Mackrory
>         Attachments: HADOOP-13760-HADOOP-13345.001.patch
>
>
> Following the S3AFileSystem integration patch in HADOOP-13651, we need to add delete tracking.
> Current behavior on delete is to remove the metadata from the MetadataStore.  To make deletes consistent, we need to add a {{isDeleted}} flag to {{PathMetadata}} and check it when returning results from functions like {{getFileStatus()}} and {{listStatus()}}.  In HADOOP-13651, I added TODO comments in most of the places these new conditions are needed.  The work does not look too bad.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org