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/09/08 16:50:46 UTC
[jira] [Issue Comment Deleted] (ATLAS-118) rename atlas log4j
configuration files to avoid config collisions with other projects
[ https://issues.apache.org/jira/browse/ATLAS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Maron updated ATLAS-118:
---------------------------------
Comment: was deleted
(was: Commit: 128a10b3f3c68dfa086aac5c7496f64ce1d1bd4e [128a10b]
Parents: 5b2136deeb
Author: Jon Maron <jm...@hortonworks.com>
Date: August 20, 2015 at 11:21:42 AM EDT
Commit Date: September 8, 2015 at 10:46:56 AM EDT
Labels: HEAD 2.3-maint
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)