| commit | 3016a2d6d1e814704f18f8992de49b8b571c051c | [log] [tgz] |
|---|---|---|
| author | su622b <su622b@att.com> | Tue Mar 31 18:43:15 2020 -0400 |
| committer | su622b <su622b@att.com> | Tue Mar 31 18:43:32 2020 -0400 |
| tree | 70b3a508f02c3c3d985d05fda2b36ec9a1690cc9 | |
| parent | feeb6d1f3e2a9b074104345ae869129b2f4dcfd5 [diff] |
fix security vulnerabilities Issue-ID: DMAAP-1418 Change-Id: I97d3f0acefa7d553c343c02b3fe6a93c3b0a5565 Signed-off-by: su622b <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