[
https://issues.apache.org/jira/browse/AMBARI-16779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300027#comment-15300027
]
Hudson commented on AMBARI-16779:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4920 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4920/])
AMBARI-16779. Zeppelin Ambari stack does not handle log4j configuration
(pallav.kul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2ca4b333d0777640e1907dc59a20daa147f69253])
*
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
*
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py
*
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml
> Zeppelin Ambari stack does not handle log4j configuration
> ---------------------------------------------------------
>
> Key: AMBARI-16779
> URL: https://issues.apache.org/jira/browse/AMBARI-16779
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Renjith Kamath
> Fix For: 2.4.0
>
> Attachments: AMBARI-16779-trunk-v1.patch
>
>
> All other components(see Knox/Spark) allow configuring log4j from Ambari UI
> except Zeppelin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
