You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/04/24 20:50:08 UTC
[jira] [Commented] (HADOOP-14416) Path starting with 'wasb:///' not
resolved correctly while authorizing with WASB-Ranger
[ https://issues.apache.org/jira/browse/HADOOP-14416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450738#comment-16450738 ]
Hudson commented on HADOOP-14416:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HADOOP-14416. Path starting with 'wasb:///' not resolved correctly while (xyao: rev 5d20b2eeab1dfbf5591e4e9eecde3517d6155bd0)
* (edit) hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/NativeAzureFileSystem.java
* (edit) hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/TestWasbRemoteCallHelper.java
* (edit) hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/MockWasbAuthorizerImpl.java
* (edit) hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/TestNativeAzureFileSystemAuthorization.java
* (edit) hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/AbstractWasbTestBase.java
> Path starting with 'wasb:///' not resolved correctly while authorizing with WASB-Ranger
> ---------------------------------------------------------------------------------------
>
> 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
> Priority: Major
> Fix For: 2.9.0, 3.0.0-alpha4
>
> Attachments: HADOOP-14416.001.patch, HADOOP-14416.001.patch, HADOOP-14416.002.patch, HADOOP-14416.003.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org