| commit | fa39dc549397b12c23096bf003b3d24016cfdd44 | [log] [tgz] |
|---|---|---|
| author | Sunil Unnava <su622b@att.com> | Mon Feb 26 13:57:22 2018 -0500 |
| committer | Sunil Unnava <su622b@att.com> | Mon Feb 26 13:57:38 2018 -0500 |
| tree | 60d1cdf5b1353f9d60b306b737950f806f285879 | |
| parent | 67cf034d0e2df6dbfb7043395671f6520972f976 [diff] |
Fixes for security isues Issue-ID: DMAAP-206 Change-Id: I8cb4fc832f364b45bdd08f9f2401630d80a488c0 Signed-off-by: Sunil Unnava <su622b@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