| commit | 1cb526d1675874ec7ffc3e6bfe2b4c89b0affa4d | [log] [tgz] |
|---|---|---|
| author | asgar <sammoham@in.ibm.com> | Fri Sep 14 15:15:54 2018 +0530 |
| committer | asgar <sammoham@in.ibm.com> | Fri Sep 14 15:16:01 2018 +0530 |
| tree | 8eefe56309e5f28027f79ce3a4ea54b2cf6ad7ef | |
| parent | 7a06eb746b2f13b2630bb5e4b5846c0a1f7d7ded [diff] |
sonar fixes in MRClientFactory.java Change-Id: Ic01e466f2a64bb02b614b48d13de65a7a48a8e74 Issue-ID: DMAAP-777 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