[ 
https://issues.apache.org/jira/browse/AMBARI-19222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754911#comment-15754911
 ] 

Hadoop QA commented on AMBARI-19222:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12843584/AMBARI-19222_branch-2.5-v1.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9706//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9706//console

This message is automatically generated.

> %livy interpreter gives 400 HttpClientError due to spark.master property 
> present in livy-spark-blacklist
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19222
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19222
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Prabhjyot Singh
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19222_branch-2.5-v1.patch
>
>
> spark.master should not be overridden because we want to use livy's own 
> default = cluster not overridden by the user via zeppelin. so it should be 
> present in the blacklist if I understand right. zeppelin should stop 
> specifying livy.spark.master in the livy interpreter in case it does so now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to