[
https://issues.apache.org/jira/browse/FLUME-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134992#comment-16134992
]
ASF subversion and git services commented on FLUME-3144:
--------------------------------------------------------
Commit 66327aa20207ca62cd7c7a4cf9e24724b5ee0dfc in flume's branch
refs/heads/trunk from [~denes]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=66327aa ]
FLUME-3144. Improve Log4jAppender's performance by allowing logging collection
of messages
Log4jAppender treats Collection messages as a special case making it possible
to log
Collection of events in one Log4j log call. The appender sends these events to
the
receiving Flume instance as one batch with the rpcClient.appendBatch() method.
This closes #151
Reviewers: Ferenc Szabo, Miklos Csanady
(Denes Arvay via Denes Arvay)
> 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)
