[
https://issues.apache.org/jira/browse/HADOOP-14416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008050#comment-16008050
]
Sivaguru Sankaridurg commented on HADOOP-14416:
-----------------------------------------------
The issue was observed on WASB secure clusters only when WASB-authorization was
enabled.
It turned out to be a problem with not normalizing paths when doing the
authorization check.
I will attach the patch to this JIRA shortly.
> Path not resolving correctly while authorizing with WASB-Ranger when it
> starts with 'wasb:///' (triple-slash)
> -------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-14416
> URL: https://issues.apache.org/jira/browse/HADOOP-14416
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure, security
> Reporter: Sivaguru Sankaridurg
> Assignee: Sivaguru Sankaridurg
>
> Bug found while launching spark-shell.
> Repro-steps :
> 1. Create a spark cluster with wasb-acls enabled.
> 2. Change spark history log directory configurations to
> wasb:///hdp/spark2-events
> 3. Launching the spark shell should fail.
> The above scenario works fine with clusters that dont have wasb-acl
> authorization enabled.
> Note : wasb:/// resolves correctly on fs shell.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
