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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/02/22 11:01:00 UTC

[jira] [Commented] (HADOOP-16134) Add S3AWriteOpContext for write ops; pass in statistics and other settings

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

Steve Loughran commented on HADOOP-16134:
-----------------------------------------

Uploaded a does-not-compile PoC of an initial design, one which  doesn't quite do it right

> Add S3AWriteOpContext for write ops; pass in statistics and other settings
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-16134
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16134
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Major
>
> As discussed in HADOOP-16090; having an {{S3AWriteOpContext}} to match the read context lets us do some interesting things
> * if we record the state of the file (is this an overwrite)? we'll know not to bother with deleting any parent dir markers (Assumption: there are none(
> * If a check for a parent dir was made (which we don't currently do, but...) then iff that was an empty dir marker, we'd know to *only* delete that marker and not go further up the tree.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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