commit | 5e5fb095d6eaa4bdbc4382344a57a6dbf648971d | [log] [tgz] |
---|---|---|
author | Varun Gudisena <vg411h@att.com> | Fri Sep 22 17:23:10 2017 -0500 |
committer | Varun Gudisena <vg411h@att.com> | Fri Sep 22 17:23:15 2017 -0500 |
tree | 6dac5e015996cd1a264c7b971fdf773584159736 | |
parent | 26b93395a6c7a6688064ce8b0ae7162327ca8fd7 [diff] |
Add new License file Removed exisitng License file and added new file. issue-id: DMAAP-145 Change-Id: I2e52295587473277f94eb25add26b174f2ce0a08 Signed-off-by: Varun Gudisena <vg411h@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