ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gautam Borad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15681) Ranger Admin/Usersync: Make log4j configurable from Ambari
Date Mon, 25 Apr 2016 13:23:12 GMT

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

Gautam Borad commented on AMBARI-15681:
---------------------------------------

Committed to trunk : https://github.com/apache/ambari/commit/ab41bca8d6cca9970b119598cc5fb5a9faa39b0f

> 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.2.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)

Mime
View raw message