atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Maron (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ATLAS-118) rename atlas log4j configuration files to avoid config collisions with other projects
Date Thu, 20 Aug 2015 15:26:45 GMT

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

Jonathan Maron resolved ATLAS-118.
----------------------------------
    Resolution: Fixed

Commit: 5b2aa81fa118c94a6d2595bbd0d779c9ae64b603 [5b2aa81]
Parents: 48343db999
Author: Jon Maron <jmaron@hortonworks.com>
Date: August 20, 2015 at 11:21:42 AM EDT
Labels: HEAD master

ATLAS-118 rename log4j.xml to atlas-log4j.xml

> 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
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> 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)

Mime
View raw message