| commit | 64d7ded68eff8bad00d2a379e23b7a8118224c23 | [log] [tgz] |
|---|---|---|
| author | asgar <sammoham@in.ibm.com> | Tue Sep 25 21:36:19 2018 +0530 |
| committer | asgar <sammoham@in.ibm.com> | Tue Sep 25 21:36:27 2018 +0530 |
| tree | fb10f22ee67626ce3b86fb09aeb7bcc9acdcca51 | |
| parent | c93fe4ad252a0e74fc5cf1f4d6c31702e8cbe62d [diff] |
added some more test cases ValidatorUtilTest.java Change-Id: Ia7a240aad73eff0c6d9944f845125677e6e5611b 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