[ 
https://issues.apache.org/jira/browse/TEZ-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366413#comment-14366413
 ] 

Siddharth Seth commented on TEZ-2176:
-------------------------------------

[~vasanthkumar] - thanks for pointing out the limitation on markers. Missed 
that bit. I think we're fine moving these messages to ERROR in that case, 
instead of depending on log4j directly.

Regarding the version change,  lets not do that in this jira. There may be 
additional bits to look at where we actually change log files using log4j APIs 
directly.

[~hitesh] - the 2.x change will be a separate jira. Will need some testing to 
see what happens if log4j2 and log4j1.x are on the classpath. Also the 
slf4j-lo4j12 / slf4j-log4j2 bindings. We can control the version shipped by Tez 
- but these may come in externally, in which case some testing will be required.

> Move all logging to slf4j
> -------------------------
>
>                 Key: TEZ-2176
>                 URL: https://issues.apache.org/jira/browse/TEZ-2176
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Vasanth kumar RJ
>         Attachments: TEZ-2176.1.patch, TEZ-2176.patch
>
>
> SLF4J supports a more comprehensive set of APIs - MDC, Formatted strings.
> Also drop commons-logging from the dependency set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to