| commit | 1a5f8f0cff97f400f5052e3dd7927f54dbcf935e | [log] [tgz] |
|---|---|---|
| author | rn509j <rn509j@att.com> | Fri Sep 29 20:05:16 2017 -0400 |
| committer | rn509j <rn509j@att.com> | Fri Sep 29 20:06:33 2017 -0400 |
| tree | 1dba0360f659d91f479934cd49fa0f5bd0e8e9ae | |
| parent | 8cc4a763e2113f82d110e56931c6fb0917e8e958 [diff] |
commiting code for test coverage DMAAP-149 Signed-off-by: rn509j <rn509j@att.com> Change-Id: Ibd7b458d618108ebf0ebd506a37ff24672a16033
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