[
https://issues.apache.org/jira/browse/ATLAS-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882098#comment-16882098
]
ASF subversion and git services commented on ATLAS-3323:
--------------------------------------------------------
Commit 2c22d62a58b4d47c6a6f0df34a15d6d0b1164a59 in atlas's branch
refs/heads/branch-2.0 from Vishal Suvagia
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2c22d62 ]
ATLAS-3323: updated log4j configuration to fix placement of maxFileSize and
maxBackupIndex
Signed-off-by: Madhan Neethiraj <[email protected]>
(cherry picked from commit d1262e995190834cca069ea365472fc61f17494f)
> Atlas log4j configurations for file-size and file-backup are wrongly placed.
> ----------------------------------------------------------------------------
>
> Key: ATLAS-3323
> URL: https://issues.apache.org/jira/browse/ATLAS-3323
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 2.0.0
> Reporter: Vishal Suvagia
> Assignee: Vishal Suvagia
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3323.patch
>
>
> Atlas log4j configurations have maxFileSize and maxBackupIndex configured
> wrongly for File, Audit, Metrics and Failed appenders. Need to move the same
> in the appender section instead of the appender/layout section.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
