[
https://issues.apache.org/jira/browse/AMBARI-15681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245401#comment-15245401
]
Hadoop QA commented on AMBARI-15681:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799185/AMBARI-15681.1.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/6499//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6499//console
This message is automatically generated.
> Ranger Admin/Usersync: Make log4j configurable from Ambari
> ----------------------------------------------------------
>
> Key: AMBARI-15681
> URL: https://issues.apache.org/jira/browse/AMBARI-15681
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-15681.1.patch, AMBARI-15681.patch
>
>
> Currently log4j configuration for Ranger Admin and UserSync cannot be updated
> from Ambari. This forces the users to directly edit the configuration file.
> In addition to making it inconvenient and inconsistent (with other services
> managed by Ambari), this would also add a manual step during migration – to
> apply any custom log4j updates to the new version config.
> Ability to directly update log4j config from Ambari would be required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
