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

Masatake Iwasaki commented on HADOOP-16104:
-------------------------------------------

I played around with the storage account in Japan East.

This issue arises when I run integration/contract tests of both wasb and abfs 
using StorageV2 account with hierarchical namespace enabled. I think straight 
forward workaround is disabling wasb tests by removing 
fs.azure.wasb.account.name and fs.contract.test.fs.wasb from 
azure-auth-keys.xml since NativeAzureFileSystem does not work with the storage 
account.

For abfs, there is already ITestGetNameSpaceEnabled which checks mismatch 
between account property and test configuration 
(fs.azure.test.namespace.enabled). I think we should just skip tests requiring 
XNS based on the value of {{AzureBlobFileSystem#getIsNamespaceEnabled}}. We 
don't need tuning knob here.

Since we can not get hierarchical namespace settings in wasb side due to 
capability of azure-storage library, adding tuning knob like 
fs.azure.test.namespace.enabled could be a option as [[email protected]] 
suggested, while I feel that fixing a wasb doc and testing_azure.md is enough 
here.

> Wasb tests to downgrade to skip when test a/c is namespace enabled
> ------------------------------------------------------------------
>
>                 Key: HADOOP-16104
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16104
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure, test
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Assignee: Masatake Iwasaki
>            Priority: Major
>
> When you run the abfs tests with a namespace-enabled accounts, all the wasb 
> tests fail "don't yet work with namespace-enabled accounts". This should be 
> downgraded to a test skip, somehow



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to