| commit | c460324eec8c605c0b8c4abbd8183cc76605260f | [log] [tgz] |
|---|---|---|
| author | Jessica Wagantall <jwagantall@linuxfoundation.org> | Fri Nov 17 12:00:43 2017 -0800 |
| committer | Jessica Wagantall <jwagantall@linuxfoundation.org> | Fri Nov 17 12:00:43 2017 -0800 |
| tree | 50419935f495c8adac903e961b813167c91f1a67 | |
| parent | 5b7869e3cf9fc3a5c09c14ba94f2d9341523c7b6 [diff] |
Bump patch version Bump patch version in preparation for Amsterdam branching. Change-Id: I0f02b162b563da6a0550f880ba4029ee1508148d Issue-ID: CIMAN-120 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
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