hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14416) Path not resolving correctly while authorizing with WASB-Ranger when it starts with 'wasb:///' (triple-slash)
Date Mon, 15 May 2017 20:58:04 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mingliang Liu updated HADOOP-14416:
-----------------------------------
    Attachment: HADOOP-14416.001.patch

> 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
>         Attachments: HADOOP-14416.001.patch, HADOOP-14416.001.patch, Non-SecureRun-Logs.txt,
SecureRunLogs.txt
>
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message