| commit | ca98537bd0271d4d3450a0bf7723bcdd5ce9d249 | [log] [tgz] |
|---|---|---|
| author | sunil unnava <sunil.unnava@att.com> | Tue Oct 30 12:28:04 2018 -0400 |
| committer | sunil unnava <sunil.unnava@att.com> | Tue Oct 30 12:29:57 2018 -0400 |
| tree | 7d90b8d8c86b087a5938fc2d0e86d3b087ae0d5f | |
| parent | 5056c3dee24ba6dfc0d0e62f9b1894d1f886e7d0 [diff] |
Fix for a license issue Issue-ID: DMAAP-871 Change-Id: I648ae0e476a8a2a07e688637e85871afee125ace 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