| commit | 85c21e1d85c545717affd3f18cd8e9fe6dc14562 | [log] [tgz] |
|---|---|---|
| author | sunil.unnava <su622b@att.com> | Tue Jan 23 15:26:15 2018 -0500 |
| committer | sunil.unnava <su622b@att.com> | Tue Jan 23 15:36:05 2018 -0500 |
| tree | 06909dffa1ac3cb95f08aa1dcebfe32708578e0a | |
| parent | 0497d0508a62ff513ff6883c2f6e1947da968d37 [diff] |
Changes to the DMaap Client Added new API to the DMaapClient Issue-ID: DMAAP-214 Change-Id: I4de2da7ca42ad1b5925a2df9d26672875dd15b10 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