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

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

commit 07060ca2302eedc651dcaffb0003ae4cd2954652
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Wed Feb 26 12:55:33 2020 +0100

    Regen documentation
---
 docs/components/modules/ROOT/pages/kafka-component.adoc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/components/modules/ROOT/pages/kafka-component.adoc 
b/docs/components/modules/ROOT/pages/kafka-component.adoc
index 4bb5162..1fa921c 100644
--- a/docs/components/modules/ROOT/pages/kafka-component.adoc
+++ b/docs/components/modules/ROOT/pages/kafka-component.adoc
@@ -38,14 +38,13 @@ kafka:topic[?options]
 
 
 // component options: START
-The Kafka component supports 10 options, which are listed below.
+The Kafka component supports 9 options, which are listed below.
 
 
 
 [width="100%",cols="2,5,^1,2",options="header"]
 |===
 | Name | Description | Default | Type
-| *brokers* (common) | 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
 | *configuration* (common) | Allows to pre-configure the Kafka component with 
common options that the endpoints will reuse. |  | KafkaConfiguration
 | *allowManualCommit* (consumer) | Whether to allow doing manual commits via 
KafkaManualCommit. If this option is enabled then an instance of 
KafkaManualCommit is stored on the Exchange message header, which allows end 
users to access this API and perform manual offset commits via the Kafka 
consumer. | false | boolean
 | *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 [...]

Reply via email to