[
https://issues.apache.org/jira/browse/HADOOP-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606617#comment-16606617
]
Da Zhou commented on HADOOP-15728:
----------------------------------
*AzureBlobFileSystem.java:*
- I will make setPermission() and setOwner() to call super method.
*AzureBlobFileSystemStore.java:*
- Since it is internal, it makes sense to remain it as it is.
*ITestAzureBlobFileSystemPermission and ITestAzureBlobFilesystemAcl:*
- I'm not moving assumeTrue(fs.getIsNamespaceEnabeld()) from the constructor
to each test method, it was checking if it is using OAuth authentication in
constructor, which doesn't make because Namespace enabled account can also use
SharedKey for authentication.
- and according to current implementation, when referring
fs.getIsNamespaceEnabeld() in test constructor there will be NULL pointer
exception because fs is not initialized.
- In ITestAzureBlobFileSystemPermission, there are tests for namespace enabled
account, and I also added tests for namespace not enabled account.
> ABFS: Add backward compatibility to handle Unsupported Operation for storage
> account with no namespace feature
> --------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-15728
> URL: https://issues.apache.org/jira/browse/HADOOP-15728
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Da Zhou
> Assignee: Da Zhou
> Priority: Major
> Attachments: HADOOP-15728-HADOOP-15407-001.patch,
> HADOOP-15728-HADOOP-15407-002.patch
>
>
> For non-namespaceenbaled account, UnsupportedOperationException is thrown
> when setOwner() or setPermission() is called, which cause problems for others.
> They should behave the same as before, so should make them no-op if the
> storage account is not namespace enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
