This is an automated email from the ASF dual-hosted git repository.

onders pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 4b584ad  Regen after typo fix
4b584ad is described below

commit 4b584ad263b7e3edf0d3dc788021a3dfd27ad1a0
Author: onders <ond...@apache.org>
AuthorDate: Mon Aug 13 15:10:29 2018 +0300

    Regen after typo fix
---
 components/camel-kafka/src/main/docs/kafka-component.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc 
b/components/camel-kafka/src/main/docs/kafka-component.adoc
index b528742..6dda59d 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -86,7 +86,7 @@ with the following path and query parameters:
 | *autoCommitEnable* (consumer) | If true, periodically commit to ZooKeeper 
the offset of messages already fetched by the consumer. This committed offset 
will be used when the process fails as the position from which the new consumer 
will begin. | true | Boolean
 | *autoCommitIntervalMs* (consumer) | The frequency in ms that the consumer 
offsets are committed to zookeeper. | 5000 | Integer
 | *autoCommitOnStop* (consumer) | Whether to perform an explicit auto commit 
when the consumer stops to ensure the broker has a commit from the last 
consumed message. This requires the option autoCommitEnable is turned on. The 
possible values are: sync, async, or none. And sync is the default value. | 
sync | String
-| *autoOffsetReset* (consumer) | What to do when there is no initial offset in 
ZooKeeper or if an offset is out of range: smallest : automatically reset the 
offset to the smallest offset largest : automatically reset the offset to the 
largest offset fail: throw exception to the consumer | latest | String
+| *autoOffsetReset* (consumer) | What to do when there is no initial offset in 
ZooKeeper or if an offset is out of range: earliest : automatically reset the 
offset to the earliest offset latest : automatically reset the offset to the 
latest offset fail: throw exception to the consumer | latest | String
 | *breakOnFirstError* (consumer) | This options controls what happens when a 
consumer is processing an exchange and it fails. If the option is false then 
the consumer continues to the next message and processes it. If the option is 
true then the consumer breaks out, and will seek back to offset of the message 
that caused a failure, and then re-attempt to process this message. However 
this can lead to endless processing of the same message if its bound to fail 
every time, eg a poison mess [...]
 | *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the 
Camel routing Error Handler, which mean any exceptions occurred while the 
consumer is trying to pickup incoming messages, or the likes, will now be 
processed as a message and handled by the routing Error Handler. By default the 
consumer will use the org.apache.camel.spi.ExceptionHandler to deal with 
exceptions, that will be logged at WARN or ERROR level and ignored. | false | 
boolean
 | *checkCrcs* (consumer) | Automatically check the CRC32 of the records 
consumed. This ensures no on-the-wire or on-disk corruption to the messages 
occurred. This check adds some overhead, so it may be disabled in cases seeking 
extreme performance. | true | Boolean

Reply via email to