[
https://issues.apache.org/jira/browse/HADOOP-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350474#comment-17350474
]
Duo Zhang commented on HADOOP-16206:
------------------------------------
I do not think it is about the difficulty, if we choose to do it then I think
we could finally get it done.
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.
For HBase, we clearly mention that for a major release, we are allowed to do
breaking changes and we will document this out.
But hadoop is another story, it is more widely used than HBase so I'm not sure
if this is the best choice...
And on testing, maybe a possible way to reduce the complexity, is to introduce
a common module with a test-jar contains a log4j2.xml, which will be used for
all other moduels to do logging when running UTs, as most of the current
log4j.properties files under src/test/resources are almost the same.
Thanks.
> 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]
