[ https://issues.apache.org/jira/browse/HADOOP-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127527#comment-13127527 ]
Hudson commented on HADOOP-7705: -------------------------------- Integrated in Hadoop-Mapreduce-0.23-Build #51 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/51/]) HADOOP-7705 stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1183291 Files : * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/Log4Json.java * /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/log/TestLog4Json.java > Add a log4j back end that can push out JSON data, one per line > -------------------------------------------------------------- > > Key: HADOOP-7705 > URL: https://issues.apache.org/jira/browse/HADOOP-7705 > Project: Hadoop Common > Issue Type: New Feature > Components: util > Affects Versions: 0.23.0, 0.24.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > Fix For: 0.23.0, 0.24.0 > > Attachments: HADOOP-7705-log4json.patch, HADOOP-7705.patch, > HADOOP-7705.patch > > > If we had a back end for Log4j that pushed out log events in single line JSON > content, we'd have something that is fairly straightforward to machine parse. > If: it may be harder to do than expected. Once working HADOOP-6244 could use > it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira