ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-4678) Custom log4j configs should be stored as raw text
Date Fri, 21 Feb 2014 23:23:21 GMT

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

Mahadev konar resolved AMBARI-4678.
-----------------------------------

    Resolution: Fixed

> Custom log4j configs should be stored as raw text
> -------------------------------------------------
>
>                 Key: AMBARI-4678
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4678
>             Project: Ambari
>          Issue Type: Task
>          Components: agent, client, controller
>    Affects Versions: 1.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> In 1.5.0, we are introducing customization of log4j.properties for various services ("hdfs-log4j"
configuration, etc).
> Instead of storing the log4j configuration as a bunch of key-value pairs, we should store
the entire log4j.properties file content as a single attribute (lets call it "content") whose
value is the entire file content of log4j.properties in raw text.
> This would be much easier for the end user to view and modify. Also, this allows us to
retain comments and logical breaks in the file.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message