[
https://issues.apache.org/jira/browse/HADOOP-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350561#comment-17350561
]
Ahmed Hussein commented on HADOOP-16206:
----------------------------------------
{quote}The problem is about compatibility... I'm sure that some end users will
use their own scripts to start a hadoop cluster, this change may break their
scripts.
{quote}
log4j used to be controlled through the properties files. If the new parameters
maintain the same default behavior (for each individual module), then this
should be acceptable.
{quote}this change may break their scripts.
{quote}
This is a good point. However, this is a part of pulling changes from trunk
into the remote forks. I do not see that a big concern as long as we are not
modifying a release.
Doing that in trunk should be acceptable.
[~aajisaka] and [~weichiu] Do you guys have any thoughts?
> Migrate from Log4j1 to Log4j2
> -----------------------------
>
> Key: HADOOP-16206
> URL: https://issues.apache.org/jira/browse/HADOOP-16206
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.3.0
> Reporter: Akira Ajisaka
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HADOOP-16206-wip.001.patch
>
>
> This sub-task is to remove log4j1 dependency and add log4j2 dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
