| commit | 646ebf1d617a028ba64423400e1e322115a8a782 | [log] [tgz] |
|---|---|---|
| author | rama-huawei <rama.subba.reddy.s@huawei.com> | Thu Sep 14 14:49:32 2017 +0530 |
| committer | Rama SubbaReddy <rama.subba.reddy.s@huawei.com> | Thu Sep 14 10:35:28 2017 +0000 |
| tree | 4505ee1b8ac8b9495ac941d956f9a70b22c1502c | |
| parent | 958e512dc08a2a2427b613e8f9c24c72905bb701 [diff] |
Fix for Sonar critical issues DCAEGEN2-93 Change-Id: I61258077212550b03eedf5387bb0282e2637dabe Signed-off-by: rama-huawei <rama.subba.reddy.s@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