hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varada Hemeswari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14768) Honoring sticky bit during Deletion when authorization is enabled in WASB
Date Fri, 22 Sep 2017 18:16:00 GMT

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

Varada Hemeswari commented on HADOOP-14768:
-------------------------------------------

[~tmarquardt] The code when auth is not enabled in patch 5 is completely the same as it used
to be previously with the exception that now the code handles delete case when delete is issued
for '/'(root path). Previously it used to throw null ponter exception. Those are the changes
you see apart from that there is clear branching when we are getting the contents to delete
the file.

Maintaining seperate paths from the beginning would be risky since changes done to one may
not be done in another. And it would be lot of duplicate code too. Also I have tested majority
of the delete scenarios in both auth enabled and disabled cases too. 

> 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, HADOOP-14768.004.patch, HADOOP-14768.005.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


Mime
View raw message