| commit | 3435526ab897d855bbd1e40eec28f9836eb91bb5 | [log] [tgz] |
|---|---|---|
| author | Mandar Sawant <ms5838@att.com> | Wed Sep 16 22:12:54 2020 -0500 |
| committer | Mandar Sawant <ms5838@att.com> | Thu Sep 17 03:21:05 2020 +0000 |
| tree | 7c176ffd7b0df161fba1b6888f2140da82482984 | |
| parent | a04e69e1f9c0dbe7c1317cc879a0fad70db83595 [diff] |
updating INFO.yaml to remove past committers Issue-ID: DMAAP-1486 Change-Id: I56826acb9dae479d58ed847ea22e9445bbb2a3e0 Signed-off-by: Mandar Sawant <ms5838@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