This is an automated email from the ASF dual-hosted git repository.
aldettinger 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 a940acd Regen
a940acd is described below
commit a940acd6a0a0582aa063c585823cbe9f479560db
Author: aldettinger <[email protected]>
AuthorDate: Mon Aug 13 22:03:15 2018 +0200
Regen
---
components/camel-kafka/src/main/docs/kafka-component.adoc | 2 +-
.../component/kafka/springboot/KafkaComponentConfiguration.java | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc
b/components/camel-kafka/src/main/docs/kafka-component.adoc
index 6dda59d..3a8cac5 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -191,7 +191,7 @@ The component supports 98 options, which are listed below.
| *camel.component.kafka.configuration.auto-commit-enable* | 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
| *camel.component.kafka.configuration.auto-commit-interval-ms* | The
frequency in ms that the consumer offsets are committed to zookeeper. | 5000 |
Integer
| *camel.component.kafka.configuration.auto-commit-on-stop* | 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
-| *camel.component.kafka.configuration.auto-offset-reset* | 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
+| *camel.component.kafka.configuration.auto-offset-reset* | 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
| *camel.component.kafka.configuration.break-on-first-error* | 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 [...]
| *camel.component.kafka.configuration.bridge-endpoint* | If the option is
true, then KafkaProducer will ignore the KafkaConstants.TOPIC header setting of
the inbound message. | false | Boolean
| *camel.component.kafka.configuration.brokers* | URL of the Kafka brokers to
use. The format is host1:port1,host2:port2, and the list can be a subset of
brokers or a VIP pointing to a subset of brokers. This option is known as
bootstrap.servers in the Kafka documentation. | | String
diff --git
a/platforms/spring-boot/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
b/platforms/spring-boot/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
index 3419d1b..07791c6 100644
---
a/platforms/spring-boot/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
+++
b/platforms/spring-boot/components-starter/camel-kafka-starter/src/main/java/org/apache/camel/component/kafka/springboot/KafkaComponentConfiguration.java
@@ -273,9 +273,9 @@ public class KafkaComponentConfiguration
private Integer fetchWaitMaxMs = 500;
/**
* 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
+ * 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
*/
private String autoOffsetReset = "latest";
/**