| commit | de993a59814af4a63496c03a823b3cdc41641f2e | [log] [tgz] |
|---|---|---|
| author | Parshad Patel <pars.patel@samsung.com> | Mon May 13 15:02:48 2019 +0900 |
| committer | Parshad Patel <pars.patel@samsung.com> | Mon May 13 15:07:18 2019 +0900 |
| tree | a413064d8e4252bba6260698487700e88ff1da34 | |
| parent | dcb1479b85dc4fa43d7e417a05d01ac153b7fd1f [diff] |
Fix too many constructor param in dmaapclient Fix Constructor has 9 parameters, which is greater than 7 authorized sonar issue. Fix Constructor has 10 parameters, which is greater than 7 authorized sonar issue. Issue-ID: DMAAP-894 Change-Id: If961a064edc165df9f96c6c5e5432ae136de4a2d Signed-off-by: Parshad Patel <pars.patel@samsung.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