You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Denes Arvay (JIRA)" <ji...@apache.org> on 2017/09/12 13:52:03 UTC

[jira] [Updated] (FLUME-3144) Improve Log4jAppender's performance by allowing logging collection of messages

     [ https://issues.apache.org/jira/browse/FLUME-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denes Arvay updated FLUME-3144:
-------------------------------
    Fix Version/s: 1.8.0

> 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
>             Fix For: 1.8.0
>
>
> 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)