| commit | 52a67e4f8b5d131d5eac1f351caebbaf2d088929 | [log] [tgz] |
|---|---|---|
| author | asgar <sammoham@in.ibm.com> | Wed Oct 03 14:17:38 2018 +0530 |
| committer | asgar <sammoham@in.ibm.com> | Wed Oct 03 14:17:44 2018 +0530 |
| tree | 06747da73fe2ef73a2a631704d446a283fe771df | |
| parent | ea2aecd64138743183bd33217ce915b0ebd1c6e6 [diff] |
added some more test cases for ValidatorUtil.java Change-Id: I5b64b56f4d1cb713547d4c8ac121188932eaf4c2 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