| commit | dcb1479b85dc4fa43d7e417a05d01ac153b7fd1f | [log] [tgz] |
|---|---|---|
| author | sunil.unnava <sunil.unnava@att.com> | Fri May 10 11:21:44 2019 -0400 |
| committer | sunil.unnava <sunil.unnava@att.com> | Fri May 10 11:22:13 2019 -0400 |
| tree | 6068acd908b981fa1055b77660211a23821c94a3 | |
| parent | ce07fa373a7f5bb876d5f31d3910baa66fd56fe1 [diff] |
clean MR codebase Issue-ID: DMAAP-1192 Change-Id: I5cc729c9a475cac859510b57542da546e1570c96 Signed-off-by: sunil.unnava <sunil.unnava@att.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