| commit | f25de1912f09ed6d5e3172332913daee1851e704 | [log] [tgz] |
|---|---|---|
| author | sunil unnava <su622b@att.com> | Fri Aug 31 11:05:31 2018 -0400 |
| committer | sunil unnava <su622b@att.com> | Fri Aug 31 11:05:52 2018 -0400 |
| tree | b0620ed26e2321ee470d8793e4bdb138e75c4f58 | |
| parent | 4cb1f9a13d30bdf0a2b4bd71b74ade305f5ff112 [diff] |
Remove the username/password check Issue-ID: DMAAP-689 Change-Id: I1b6528bd3aaa2d9d117d0970444123a3c93ac597 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