commit | 6953e6169bb7b92a41a902e3ad932c88aab38bb5 | [log] [tgz] |
---|---|---|
author | Marcin Migdal <marcin.migdal@nokia.com> | Wed Jun 20 14:56:52 2018 +0200 |
committer | Marcin Migdal <marcin.migdal@nokia.com> | Thu Jun 21 08:48:22 2018 +0200 |
tree | 603a6efb2d35ce05503a5299e5145759fba441ee | |
parent | 2721925ea824afb932b09aa9575fdb35311325d7 [diff] |
JUnit against ToolsUtil Found missing one Change-Id: Iee604b30e9b2dcdb88f42916b1be01bf3de965fe Issue-ID: DMAAP-518 Signed-off-by: Marcin Migdal <marcin.migdal@nokia.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