commit | 0cb18b0baa2cf750e557262d821bbf2a03326bbe | [log] [tgz] |
---|---|---|
author | sunil unnava <sunil.unnava@att.com> | Tue Oct 23 10:31:46 2018 -0400 |
committer | sunil unnava <sunil.unnava@att.com> | Tue Oct 23 10:33:54 2018 -0400 |
tree | 8ca6880c9cc4f3bfc9d76575ef03ca647863415a | |
parent | 9775bb11c919b0a8d89d81abf1b1a76bb7592f78 [diff] |
update the package name Issue-ID: DMAAP-858 Change-Id: Ia69621ea6ad2ec2ec525800af2a7d3f73aef82ed 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