| commit | c5a7332b4eb975fd0e50b5dfd80c1d655a246a9a | [log] [tgz] |
|---|---|---|
| author | Rupinder <rupinsi1@in.ibm.com> | Thu May 21 15:12:08 2020 +0530 |
| committer | Rupinder <rupinsi1@in.ibm.com> | Thu May 21 15:12:16 2020 +0530 |
| tree | 9fa0d99c0f4a4451faecb44fdcc28de5f99620d0 | |
| parent | ebbbdfe1543809bc044781f3ce30e65d106e21d8 [diff] |
fixed some JUnits Issue-ID: DMAAP-1415 Change-Id: I22386744f2d015bd7a9aeb1ee3a6aa47fcb475a2 Signed-off-by: Rupinder <rupinsi1@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