[
https://issues.apache.org/jira/browse/ATLAS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705437#comment-14705437
]
Venkatesh Seetharam commented on ATLAS-118:
-------------------------------------------
Not sure how this can be prudent - this is overriding the default behavior of
log4j framework - I see that this is overridden in a lot of places and is quite
fragile. Introduces a lot of issues if we add new code and forget to make sure
its not the default log4j file.
Simplest possible solution was to not bundle the file in the jar file.
> 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)
