| commit | 37b7b57fc51f25079b13a016945e5e1f318dc361 | [log] [tgz] |
|---|---|---|
| author | su622b <sunil.unnava@att.com> | Mon Apr 09 18:51:28 2018 -0400 |
| committer | su622b <sunil.unnava@att.com> | Mon Apr 09 18:51:45 2018 -0400 |
| tree | ae1c90222297eaad8998987921cbb2dda133d8de | |
| parent | 20f5a4a523b284437dc7f76d2bc012ebb4cd669b [diff] |
Support for post without auth Issue-ID: DMAAP-399 Change-Id: I51f1ff8ed978e3e00fccd63edf421c794f6e7f32 Signed-off-by: su622b <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