commit | 050efb3743cc127f2f3a3298d6731dd926994cd2 | [log] [tgz] |
---|---|---|
author | su622b <su622b@att.com> | Wed Nov 20 15:13:53 2019 -0500 |
committer | sunil unnava <su622b@att.com> | Wed Nov 20 20:45:01 2019 +0000 |
tree | f5b121be0bd78ade86bbc9c2b5118fcc05b5035e | |
parent | 5d8ec67db97bdb61b0c07c46afb3a58a02661274 [diff] |
update oparent to 2.1.0 Issue-ID: DMAAP-1341 Change-Id: I7870f3654e7ae3155ecd3a19f2b2e75ba20b336f Signed-off-by: su622b <su622b@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