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

Hadoop QA commented on AMBARI-19651:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12848879/AMBARI-19651.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/10196//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10196//console

This message is automatically generated.

> Allow user to add custom property for log4j
> -------------------------------------------
>
>                 Key: AMBARI-19651
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19651
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19651_branch-2.5.patch, AMBARI-19651.patch
>
>
> Existing rolling properties like MaxFileSize and MaxBackupIndex for various 
> services have been parameterized for ease of use by end user.
> These properties have been added for those services which did not originally 
> have it.
> During Ambari Upgrade, user will not be able to see these changes. One way is 
> to document how the user can manually make use of this feature by adding a 
> custom-log4j property as well as change the template with the same variable 
> name as used in the backend python file. This jira is to make UI changes in 
> order to allow user to add custom-log4j properties if they want to after an 
> ambari upgrade.



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

Reply via email to