[
https://issues.apache.org/jira/browse/FLUME-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135032#comment-16135032
]
Hudson commented on FLUME-3144:
-------------------------------
UNSTABLE: Integrated in Jenkins build Flume-trunk-hbase-1 #307 (See
[https://builds.apache.org/job/Flume-trunk-hbase-1/307/])
FLUME-3144. Improve Log4jAppender's performance by allowing logging (denes:
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=66327aa20207ca62cd7c7a4cf9e24724b5ee0dfc])
* (edit)
flume-ng-clients/flume-ng-log4jappender/src/test/java/org/apache/flume/clients/log4jappender/TestLog4jAppenderWithAvro.java
* (edit)
flume-ng-clients/flume-ng-log4jappender/src/main/java/org/apache/flume/clients/log4jappender/Log4jAppender.java
* (edit) flume-ng-clients/flume-ng-log4jappender/pom.xml
* (edit)
flume-ng-clients/flume-ng-log4jappender/src/test/java/org/apache/flume/clients/log4jappender/TestLog4jAppender.java
> Improve Log4jAppender's performance by allowing logging collection of messages
> ------------------------------------------------------------------------------
>
> Key: FLUME-3144
> URL: https://issues.apache.org/jira/browse/FLUME-3144
> Project: Flume
> Issue Type: Improvement
> Affects Versions: 1.7.0
> Reporter: Denes Arvay
> Assignee: Denes Arvay
>
> Currently it's only possible to send events one by one with the Log4j
> appender. (Except if the events are wrapped in an avro record but it's quite
> cumbersome and might need special handling on the receiving side)
> As the Log4j methods can handle any {{Object}} I'd suggest to improve the
> Log4j appender to treat {{Collection}} event as a special case and send its
> content to Flume with one {{rpcClient.appendBatch()}} call.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
