[ 
https://issues.apache.org/jira/browse/AMBARI-15681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gautam Borad updated AMBARI-15681:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

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

Reply via email to