[
https://issues.apache.org/jira/browse/HADOOP-16104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771259#comment-16771259
]
Masatake Iwasaki commented on HADOOP-16104:
-------------------------------------------
[[email protected]] thanks for the input. Tests using
AbstractAbfsIntegrationTest#getWasbFileSystem such as
ITestAzureBlobFileSystemRandomRead and ITestWasbAbfsCompatibility already have
a guard as you say.
{code:java}
public void testListFileStatus() throws Exception {
// crate file using abfs
AzureBlobFileSystem fs = getFileSystem();
// test only valid for non-namespace enabled account
Assume.assumeFalse("Namespace enabled account does not support this test,",
fs.getIsNamespaceEnabled());
NativeAzureFileSystem wasb = getWasbFileSystem();
{code}
I tested attached 001 in Japan region. Wasb integration/contract tests are
skipped on account with hierarchical namespace if I set
fs.azure.test.namespace.enabled true in azure-test.xml and wasb.xml. Does this
work for you?
> 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
> Attachments: HADOOP-16104.001.patch
>
>
> 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]