Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 12 May 2017 12:33:04 +0000 (UTC)
From: "Sivaguru Sankaridurg (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13071520.1494592355000.197069.1494592384026@Atlassian.JIRA>
In-Reply-To: <JIRA.13071520.1494592355000@Atlassian.JIRA>
References: <JIRA.13071520.1494592355000@Atlassian.JIRA> <JIRA.13071520.1494592355071@jira-lw-us.apache.org>
Subject: [jira] [Created] (HADOOP-14416) Path not resolving correctly while
 authorizing with WASB-Ranger when it starts with 'wasb:///' (triple-slash)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 12 May 2017 12:33:10 -0000

Sivaguru Sankaridurg created HADOOP-14416:
---------------------------------------------

             Summary: 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org