[
https://issues.apache.org/jira/browse/HADOOP-14416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011313#comment-16011313
]
Hadoop QA commented on HADOOP-14416:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
4s{color} | {color:blue} The patch file was not named according to hadoop's
naming conventions. Please see https://wiki.apache.org/hadoop/HowToContribute
for instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HADOOP-14416 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14416 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12867776/Non-SecureRun-Logs.txt
|
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/12320/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
