[
https://issues.apache.org/jira/browse/HADOOP-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199818#comment-16199818
]
Varada Hemeswari commented on HADOOP-14913:
-------------------------------------------
Also I have enabled the tests to run by default without skipping for the
following test classes with the [^HADOOP-14913-003.patch] so the anyone running
the command
{code}
mvn -T 1c -Dparallel-tests -DtestsThreadCount=8 clean verify
{code}
do not have to enable any secure flag to run these tests.
So these will not skip now - TestNativeAzureFileSystemAuthorization.java,
ITestNativeAzureFSAuthWithBlobSpecificKeys.java,
ITestNativeAzureFSAuthorizationCaching.java,
> Sticky bit implementation for Rename operation in Azure fs
> ----------------------------------------------------------
>
> Key: HADOOP-14913
> URL: https://issues.apache.org/jira/browse/HADOOP-14913
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs, fs/azure
> Reporter: Varada Hemeswari
> Assignee: Varada Hemeswari
> Labels: azure, fs, secure
> Attachments: HADOOP-14193.001.patch, HADOOP-14193.002.patch,
> HADOOP-14913-003.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/rename 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 'rename'
> call when authorization is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
