| commit | d45a6e11be79157fb32e5cd6252a14747406e20f | [log] [tgz] |
|---|---|---|
| author | sunil unnava <su622b@att.com> | Fri Aug 31 14:39:10 2018 -0400 |
| committer | sunil unnava <su622b@att.com> | Fri Aug 31 14:39:33 2018 -0400 |
| tree | a89afb3ae89574746e325b396ca7c0f5731036ce | |
| parent | f25de1912f09ed6d5e3172332913daee1851e704 [diff] |
Fix the typo error in the error message Issue-ID: DMAAP-688 Change-Id: I5457bf0829fa509e932e2e814ed4b9e9a21ce2e5 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