[
https://issues.apache.org/jira/browse/HADOOP-18207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729032#comment-17729032
]
Duo Zhang commented on HADOOP-18207:
------------------------------------
This is a problem that I've been a branch committer in the past but actually,
there is no such thing in the official ASF processes, so I will be listed as a
'member' on github, and others may consider I'm a committer of hadoop...
Anyway, I could try to contribute more on hadoop and finally become a committer
of hadoop so everyone will be happy...
And for this patch, it is not merged by me. [~weichiu] has also skimmed the
patch and then merged it, I think we can have a implicit +1 from him? If
[~ayushtkn] you think this is not valid, we can revert it and let [~vjasani]
open a new PR with the addendum integrated, and then we merge it again with an
explicit +1 from hadoop committers. Or we could just merge the addendum quickly
so it will not break our jenkins jobs.
WDYT?
Thanks.
> Introduce hadoop-logging module
> -------------------------------
>
> Key: HADOOP-18207
> URL: https://issues.apache.org/jira/browse/HADOOP-18207
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> There are several goals here:
> # Provide the ability to change log level, get log level, etc.
> # Place all the appender implementation(?)
> # Hide the real logging implementation.
> # Later we could remove all the log4j references in other hadoop module.
> # Move as much log4j usage to the module as possible.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
