| commit | bc1cad19ab499422b902bf8a2ee2c9900c03e906 | [log] [tgz] |
|---|---|---|
| author | su622b <sunil.unnava@att.com> | Fri Apr 06 13:19:14 2018 -0400 |
| committer | su622b <sunil.unnava@att.com> | Fri Apr 06 13:19:39 2018 -0400 |
| tree | a8c415d27f270adfbcd9a6983e780545c490f565 | |
| parent | 2b34b699cdb91127f9437b1e2f7763bcdfefe6aa [diff] |
Fixes for response parsing errors Issue-ID: DMAAP-396 Change-Id: I2d8fa85dfe5246d76cf4e2066f4c5e6859c4440f Signed-off-by: su622b <sunil.unnava@att.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