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] [Updated] (HADOOP-14768) Honoring sticky bit during Deletion when authorization is enabled in WASB
Date Mon, 18 Sep 2017 13:50:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Varada Hemeswari updated HADOOP-14768:
--------------------------------------
    Attachment: HADOOP-14768.004.patch

Did a pull of integration tests commit.

I see a test failing in non-secure mode after the pull. Not sure how it is related to my changes.

testCredsFromCredentialProvider(org.apache.hadoop.fs.azure.ITestWasbUriAndConfiguration) 
Time elapsed: 0.221 sec  <<< FAILURE!
java.lang.AssertionError: AccountKey incorrect. expected:<testkey> but was:<null>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:743)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at org.apache.hadoop.fs.azure.ITestWasbUriAndConfiguration.testCredsFromCredentialProvider(ITestWasbUriAndConfiguration.java:347)

> 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.



--
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