This is an automated email from the ASF dual-hosted git repository.
davsclaus 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 5c3fa7b Regen
5c3fa7b is described below
commit 5c3fa7b6172958c340d9e05c230e8bbc6f4e6a07
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Oct 2 05:30:25 2019 +0200
Regen
---
components/camel-kafka/src/main/docs/kafka-component.adoc | 4 +---
docs/components/modules/ROOT/pages/kafka-component.adoc | 4 +---
docs/user-manual/modules/ROOT/pages/resequence-eip.adoc | 2 +-
3 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc
b/components/camel-kafka/src/main/docs/kafka-component.adoc
index e4b83450..558df29 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 @@ When using Spring Boot make sure to use the following Maven
dependency to have s
----
-The component supports 100 options, which are listed below.
+The component supports 98 options, which are listed below.
@@ -208,11 +208,9 @@ The component supports 100 options, which are listed below.
| *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:
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 <tt>false</tt> then the consumer continues to the next message
and processes it. If the option is <tt>true</tt> 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 [...]
-| *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. <p/> This option is known as
<tt>bootstrap.servers</tt> in the Kafka documentation. | | String
| *camel.component.kafka.configuration.buffer-memory-size* | The total bytes
of memory the producer can use to buffer records waiting to be sent to the
server. If records are sent faster than they can be delivered to the server the
producer will either block or throw an exception based on the preference
specified by block.on.buffer.full.This setting should correspond roughly to the
total memory the producer will use, but is not a hard bound since not all
memory the producer uses is used [...]
| *camel.component.kafka.configuration.check-crcs* | 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
-| *camel.component.kafka.configuration.circular-topic-detection* | If the
option is true, then KafkaProducer will detect if the message is attempted to
be sent back to the same topic it may come from, if the message was original
from a kafka consumer. If the KafkaConstants.TOPIC header is the same as the
original kafka consumer topic, then the header setting is ignored, and the
topic of the producer endpoint is used. In other words this avoids sending the
same message back to where it ca [...]
| *camel.component.kafka.configuration.client-id* | The client id is a
user-specified string sent in each request to help trace calls. It should
logically identify the application making the request. | | String
| *camel.component.kafka.configuration.compression-codec* | This parameter
allows you to specify the compression codec for all data generated by this
producer. Valid values are "none", "gzip" and "snappy". | none | String
| *camel.component.kafka.configuration.connection-max-idle-ms* | Close idle
connections after the number of milliseconds specified by this config. | 540000
| Integer
diff --git a/docs/components/modules/ROOT/pages/kafka-component.adoc
b/docs/components/modules/ROOT/pages/kafka-component.adoc
index adb01f4..437a0f2 100644
--- a/docs/components/modules/ROOT/pages/kafka-component.adoc
+++ b/docs/components/modules/ROOT/pages/kafka-component.adoc
@@ -192,7 +192,7 @@ When using Spring Boot make sure to use the following Maven
dependency to have s
----
-The component supports 100 options, which are listed below.
+The component supports 98 options, which are listed below.
@@ -209,11 +209,9 @@ The component supports 100 options, which are listed below.
| *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:
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 <tt>false</tt> then the consumer continues to the next message
and processes it. If the option is <tt>true</tt> 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 [...]
-| *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. <p/> This option is known as
<tt>bootstrap.servers</tt> in the Kafka documentation. | | String
| *camel.component.kafka.configuration.buffer-memory-size* | The total bytes
of memory the producer can use to buffer records waiting to be sent to the
server. If records are sent faster than they can be delivered to the server the
producer will either block or throw an exception based on the preference
specified by block.on.buffer.full.This setting should correspond roughly to the
total memory the producer will use, but is not a hard bound since not all
memory the producer uses is used [...]
| *camel.component.kafka.configuration.check-crcs* | 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
-| *camel.component.kafka.configuration.circular-topic-detection* | If the
option is true, then KafkaProducer will detect if the message is attempted to
be sent back to the same topic it may come from, if the message was original
from a kafka consumer. If the KafkaConstants.TOPIC header is the same as the
original kafka consumer topic, then the header setting is ignored, and the
topic of the producer endpoint is used. In other words this avoids sending the
same message back to where it ca [...]
| *camel.component.kafka.configuration.client-id* | The client id is a
user-specified string sent in each request to help trace calls. It should
logically identify the application making the request. | | String
| *camel.component.kafka.configuration.compression-codec* | This parameter
allows you to specify the compression codec for all data generated by this
producer. Valid values are "none", "gzip" and "snappy". | none | String
| *camel.component.kafka.configuration.connection-max-idle-ms* | Close idle
connections after the number of milliseconds specified by this config. | 540000
| Integer
diff --git a/docs/user-manual/modules/ROOT/pages/resequence-eip.adoc
b/docs/user-manual/modules/ROOT/pages/resequence-eip.adoc
index c3acb5d..0eb82e8 100644
--- a/docs/user-manual/modules/ROOT/pages/resequence-eip.adoc
+++ b/docs/user-manual/modules/ROOT/pages/resequence-eip.adoc
@@ -66,7 +66,7 @@ Typically you'd use a header rather than the body to order
things; or maybe a pa
[source,java]
----
-resequencer(header("mySeqNo"))
+resequence(header("mySeqNo"))
----
for example to reorder messages using a custom sequence number in the header
`mySeqNo`. +
