| commit | 9775bb11c919b0a8d89d81abf1b1a76bb7592f78 | [log] [tgz] |
|---|---|---|
| author | asgar <sammoham@in.ibm.com> | Mon Oct 08 20:14:31 2018 +0530 |
| committer | asgar <sammoham@in.ibm.com> | Mon Oct 08 20:14:37 2018 +0530 |
| tree | ed0f6c3317d9555aa01e6af99d8bd53e9022369a | |
| parent | e124aeeb689db8959f6dbee88402624ff5ea3f20 [diff] |
one more case added in DmaapClientUtilTest.java Change-Id: Ifaa597832166063a16f5b27c5cc9ad390dbe41b1 Issue-ID: DMAAP-838 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