[
https://issues.apache.org/jira/browse/FLUME-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085068#comment-13085068
]
Chris Jansen commented on FLUME-743:
------------------------------------
I've been working on a fix for this as per the flume-user mailing list here:
http://mail-archives.apache.org/mod_mbox/incubator-flume-user/201108.mbox/%3CCANpnisohwf6UqEgPyMxcFBSMutxXTvzbUVXPKe4A4=xxk+5...@mail.gmail.com%3E
More than happy to be assigned this issue myself.
> Log4J Avro Appender Ignores Logging Pattern
> -------------------------------------------
>
> Key: FLUME-743
> URL: https://issues.apache.org/jira/browse/FLUME-743
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v0.9.4
> Environment: Linux Ubuntu/Redhat
> Reporter: Chris Jansen
> Priority: Minor
> Labels: log4j
>
> The log4J Avro appender does not use the pattern layout to format event
> messages. It only takes the message body, meaning that important information
> such as thread name, MDC/NDC values and stacktrace are lost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira