GitHub user adenes opened a pull request:
https://github.com/apache/flume/pull/151
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.
New tests added:
- logging of a collection of multiple strings, expect one `appendBatch()`
call.
- logging one string, expect one `append()` call.
- logging of a singleton collection of a string, expect one `append()` call.
- logging of an empty collection, expect that neither `append()` nor
`appendBatch()` was called.
- logging of a `String` and an arbitrary object in one collection with
`AvroReflectionEnabled` set to `true`
- logging of a `String` and an arbitrary object in one collection with
`AvroReflectionEnabled` set to `false`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/adenes/flume FLUME-3144
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flume/pull/151.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #151
commit ba4a9a9793104be715d451cc06c42ac73a77e00e
Author: Denes Arvay
Date: 2017-08-11T14:22:04Z
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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
