| commit | 7a06eb746b2f13b2630bb5e4b5846c0a1f7d7ded | [log] [tgz] |
|---|---|---|
| author | asgar <sammoham@in.ibm.com> | Wed Sep 12 13:52:24 2018 +0530 |
| committer | asgar <sammoham@in.ibm.com> | Wed Sep 12 13:56:50 2018 +0530 |
| tree | 53cd21034c6c1b9b4f8b6456ad15c6e782d99707 | |
| parent | d45a6e11be79157fb32e5cd6252a14747406e20f [diff] |
couple of fixes in MRClientBuilders.java Change-Id: Iad8229ec47c2fc08390f203edeb51acd74058e61 Issue-ID: DMAAP-770 Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.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