[
https://issues.apache.org/jira/browse/HADOOP-16617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Bokor updated HADOOP-16617:
----------------------------------
Description:
AzureBlobFileSystemStore#getIsNamespaceEnabled() gets ACL status of root path
to decide whether the account is XNS or not. If not it returns with 400 as
error code which means the account is a non-XNS acc.
The problem is that we get 400 and the getIsNamespaceEnabled return false even
if the filesystem does not exist which seems ok but according to the test we
should get 404. So it seems the expected behavior is to return 404.
At this point I am not sure how to fix it. Should we insist to the expected
behavior and fix it on server side or we just adjust the test to expect false
in case of non XNS account?
was:
AzureBlobFileSystemStore#getIsNamespaceEnabled() gets ACL status of root path
to decide whether the account is XNS or not. If not it return with 400 as error
code which means the account is a non-XNS acc.
The problem is that we get 400 and the getIsNamespaceEnabled return false even
if the filesystem does not exist which seems ok but according to the test we
should get 404. So it seems the expected behavior is to return 404.
At this point I am not sure how to fix it. Should we insist to the expected
behavior and fix it on server side or we just adjust the test to expect false
in case of non XNS account?
> ITestGetNameSpaceEnabled#testFailedRequestWhenFSNotExist fails with ns
> disabled account
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-16617
> URL: https://issues.apache.org/jira/browse/HADOOP-16617
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Andras Bokor
> Assignee: Andras Bokor
> Priority: Major
>
> AzureBlobFileSystemStore#getIsNamespaceEnabled() gets ACL status of root path
> to decide whether the account is XNS or not. If not it returns with 400 as
> error code which means the account is a non-XNS acc.
> The problem is that we get 400 and the getIsNamespaceEnabled return false
> even if the filesystem does not exist which seems ok but according to the
> test we should get 404. So it seems the expected behavior is to return 404.
> At this point I am not sure how to fix it. Should we insist to the expected
> behavior and fix it on server side or we just adjust the test to expect false
> in case of non XNS account?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
