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 2017/09/20 13:08:00 UTC
[jira] [Comment Edited] (HADOOP-14768) Honoring sticky bit during
Deletion when authorization is enabled in WASB
[ https://issues.apache.org/jira/browse/HADOOP-14768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173143#comment-16173143 ]
Steve Loughran edited comment on HADOOP-14768 at 9/20/17 1:07 PM:
------------------------------------------------------------------
To submit a patch you need to
# add a new file: the most recent file added is always taken to be the patch
# hit "cancel patch"
# hit "submit path"
# wait
The build is [in Jenkins|https://builds.apache.org/view/H-L/view/Hadoop/job/PreCommit-HADOOP-Build/] if you want to see what's going on
Note: you must add a new file; cancel & submit isn't enough to trigger a job. You can just re-attach the previous file
was (Author: stevel@apache.org):
To submit a patch you need to
# add a new file: the most recent file added is always taken to be the patch
# hit "cancel patch"
# hit "submit path"
# wait
The build is [in Jenkins|https://builds.apache.org/view/H-L/view/Hadoop/job/PreCommit-HADOOP-Build/] if you want to see what's going on
> Honoring sticky bit during Deletion when authorization is enabled in WASB
> -------------------------------------------------------------------------
>
> Key: HADOOP-14768
> URL: https://issues.apache.org/jira/browse/HADOOP-14768
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Reporter: Varada Hemeswari
> Assignee: Varada Hemeswari
> Labels: fs, secure, wasb
> Attachments: HADOOP-14768.001.patch, HADOOP-14768.002.patch, HADOOP-14768.003.patch, HADOOP-14768.003.patch, HADOOP-14768.004.patch
>
>
> When authorization is enabled in WASB filesystem, there is a need for stickybit in cases where multiple users can create files under a shared directory. This additional check for sticky bit is reqired since any user can delete another user's file because the parent has WRITE permission for all users.
> The purpose of this jira is to implement sticky bit equivalent for 'delete' call when authorization is enabled.
> Note : Sticky bit implementation for 'Rename' operation is not done as part of this JIRA
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org