commit | 1f70b26884ba61f466eac21635eae125acd29a1f | [log] [tgz] |
---|---|---|
author | Lee, Tian (tl5884) <TianL@amdocs.com> | Tue Jul 10 14:15:52 2018 +0100 |
committer | Lee, Tian (tl5884) <TianL@amdocs.com> | Tue Jul 10 14:48:25 2018 +0100 |
tree | d6f31ff2c650b96c1ddd3af57c2b5eb07ac33054 | |
parent | 6953e6169bb7b92a41a902e3ad932c88aab38bb5 [diff] |
Fix various Sonar issues in MRConsumerImpl Amendment 1: Restructure order of methods and fields according to Java convention. Amendment 2: Remove bug fix that was accidentally included. This will be committed in a separate commit. These changes do not affect the original functionality of the class. Change-Id: I974a5e3fa94ca184704c4e26636bcbbfb5ce3320 Issue-ID: DMAAP-540 Signed-off-by: Lee, Tian (tl5884) <TianL@amdocs.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