| commit | 2721925ea824afb932b09aa9575fdb35311325d7 | [log] [tgz] |
|---|---|---|
| author | sunil unnava <su622b@att.com> | Thu Jun 14 18:05:40 2018 -0400 |
| committer | sunil unnava <su622b@att.com> | Thu Jun 14 18:07:36 2018 -0400 |
| tree | ff0f4ee805254ea05873ece12b9b928872d7f2a5 | |
| parent | 5519f8372acf8d4f573739b8e819f7a1e569a019 [diff] |
fixes for null pointer exceptions Issue-ID: DMAAP-519 Change-Id: Ia32d0bd58c5f438b50e361221a96b988b00a1120 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