| commit | 41de45350f283e110caa3709a55cb7f306b631bb | [log] [tgz] |
|---|---|---|
| author | Sunil Unnava <su622b@att.com> | Thu Mar 08 13:50:34 2018 -0500 |
| committer | Sunil Unnava <su622b@att.com> | Thu Mar 08 13:51:21 2018 -0500 |
| tree | 4c731289b822d27b54a286e65dfad49635779737 | |
| parent | 173a07c146746f85c17f2d58f2ded84b99818f9a [diff] |
fixes for security issues Issue-ID: DMAAP-206 Change-Id: If7a5f5bf5c8fa8cb7cdabc47e6d1eed4ca43c2cf 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