| commit | e2e093ee2fd0ac75491bf6ce060339b19b4a7039 | [log] [tgz] |
|---|---|---|
| author | Gildas Lanilis <gildas.lanilis@huawei.com> | Thu Mar 15 17:39:27 2018 -0700 |
| committer | Gildas Lanilis <gildas.lanilis@huawei.com> | Thu Mar 15 17:40:09 2018 -0700 |
| tree | 5c30426bed3e9525aa4eeeef6d66f016bbd7d1e1 | |
| parent | 41de45350f283e110caa3709a55cb7f306b631bb [diff] |
Upgrade to latest oparent Update pom.xml file to latest version release of oparent, 1.1.0 Change-Id: Ie0f811137ba4a988e7226a81ea486a1452fc6a03 Issue-ID: INT-443 Signed-off-by: Gildas Lanilis <gildas.lanilis@huawei.com>
To configure a MR Log4J appender the following parameters are available:
(R) Topic [String] - The topic which you wish to publish your log messages to (R) Partition [String]- The partition within the Topic that you wish you publish your log messages to (R) Hosts [String]- A comma separated string containing the MR API server nodes you wish to connect to (O) MaxBatchSize [Integer] - The maximum size of the batch of log messages. When the batch grows larger than this, the messages are flushed to the topic/partition. (O) MaxAgeMs [Integer] - The maximum age in milliseconds of the batch. When the batch age is older than this, the messages are flushed to the topic/partition. (O) Compress [Boolean] - Indicates whether you would like your messages compressed or not.
An example can be found in ./src/main/resources/log4j.xml