| commit | ea2aecd64138743183bd33217ce915b0ebd1c6e6 | [log] [tgz] |
|---|---|---|
| author | asgar <sammoham@in.ibm.com> | Thu Sep 27 19:54:29 2018 +0530 |
| committer | asgar <sammoham@in.ibm.com> | Thu Sep 27 19:54:35 2018 +0530 |
| tree | a9ffcbecc0203ad4be28d41057fee520a25fa800 | |
| parent | 64d7ded68eff8bad00d2a379e23b7a8118224c23 [diff] |
added couple of cases for ValidatorUtil.java Change-Id: I9be3ab9ef2b745c3b2fc54ff73a780fec176ec40 Issue-ID: DMAAP-809 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