| commit | e709bb9923625f1f36cd5890d86b8cfa01d05739 | [log] [tgz] |
|---|---|---|
| author | sunil.unnava <sunil.unnava@att.com> | Wed Apr 03 16:31:03 2019 -0400 |
| committer | sunil.unnava <sunil.unnava@att.com> | Wed Apr 03 16:31:20 2019 -0400 |
| tree | ff97b222986c3b77f46f75013b575ece4d906311 | |
| parent | e3da91b4013e3c4fea1d2a2c6f0e4a1677fb3ba4 [diff] |
add testcases Issue-ID: DMAAP-1147 Change-Id: I2e8f5fdf3aba2b3667b6bd505cd56e48798a465b 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