You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Jonathan Maron (JIRA)" <ji...@apache.org> on 2015/08/20 16:08:46 UTC

[jira] [Created] (ATLAS-118) rename atlas log4j configuration files to avoid config collisions with other projects

Jonathan Maron created ATLAS-118:
------------------------------------

             Summary: rename atlas log4j configuration files to avoid config collisions with other projects
                 Key: ATLAS-118
                 URL: https://issues.apache.org/jira/browse/ATLAS-118
             Project: Atlas
          Issue Type: Bug
    Affects Versions: 0.6-incubating
            Reporter: Jonathan Maron
            Assignee: Jonathan Maron
             Fix For: 0.6-incubating


There appear to be instances in which using the default name for log4j configuration (e.g. log4j.xml) will cause the atlas version of the file to be picked up and utilized by other projects (e.g. hive/hcat).  This can actually lead to issues with the functionality of other projects, especially if they are dependent on log parsing.  

The log4j.xml file will be renamed to atlas-log4j.xml and explicitly referenced from the scripts via the 'log4j.configuration' system property.



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