| commit | 2ce8d15a4d5c03bb4f2f676114c466b61c4a3188 | [log] [tgz] |
|---|---|---|
| author | Arindam Mondal <arind.mondal@samsung.com> | Fri Mar 15 18:54:33 2019 +0900 |
| committer | arind.mondal <arind.mondal@samsung.com> | Fri Mar 15 18:55:09 2019 +0900 |
| tree | fbcffa5254cee1994a98a8419e5f04bd7566a2e2 | |
| parent | 818d445756d518be0f09706677f402b9d567d70b [diff] |
Sonar fix too many method param Issue-ID: DMAAP-1099 Change-Id: Id659edc743c76e8a56cbb39d0185bff5c50f36a3 Signed-off-by: Arindam Mondal <arind.mondal@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