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
The following commit(s) were added to refs/heads/master by this push:
new 7a2ffcf Regen for commit 952b4a81df9c50d5bb0df63785b32283e1cdcbeb
7a2ffcf is described below
commit 7a2ffcf60c0e32d08172b69eed673c342b123744
Author: omarsmak <[email protected]>
AuthorDate: Tue Apr 13 09:03:08 2021 +0000
Regen for commit 952b4a81df9c50d5bb0df63785b32283e1cdcbeb
Signed-off-by: GitHub <[email protected]>
---
.../resources/org/apache/camel/catalog/docs/vertx-kafka-component.adoc | 1 +
docs/components/modules/ROOT/pages/vertx-kafka-component.adoc | 1 +
2 files changed, 2 insertions(+)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/vertx-kafka-component.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/vertx-kafka-component.adoc
index 9eaa5ed..6c86bf5 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/vertx-kafka-component.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/vertx-kafka-component.adoc
@@ -343,6 +343,7 @@ Before sending a message to Kafka you can configure the
following headers.
|`CamelVertxKafkaMessageKey`| `VertxKafkaConstants.MESSAGE_KEY`|`String`|
Explicitly specify the message key, if partition ID is not specified, this will
trigger the messages to go into the same partition.
|`CamelVertxKafkaTopic`| `VertxKafkaConstants.TOPIC`|`String`| Explicitly
specify the topic to where produce the messages, this will be *preserved* in
case of header aggregation.
|`CamelVertxKafkaOverrideTopic`|
`VertxKafkaConstants.OVERRIDE_TOPIC`|`String`| Explicitly specify the topic to
where produce the messages, this will *not be preserved* in case of header
aggregation and it will take *precedence* over `CamelVertxKafkaTopic`.
+| `CamelVertxKafkaOverrideTimestamp` |
`VertxKafkaConstants.OVERRIDE_TIMESTAMP` | Long | The ProducerRecord also has
an associated timestamp. If the user did provide a timestamp, the producer will
stamp the record with the provided timestamp and the header is not preserved.
|=======================================================================
If you want to send a message to a dynamic topic then use
`VertxKafkaConstants.OVERRIDE_TOPIC` as its used as a one-time header
diff --git a/docs/components/modules/ROOT/pages/vertx-kafka-component.adoc
b/docs/components/modules/ROOT/pages/vertx-kafka-component.adoc
index 1c48d0d..e3d9950 100644
--- a/docs/components/modules/ROOT/pages/vertx-kafka-component.adoc
+++ b/docs/components/modules/ROOT/pages/vertx-kafka-component.adoc
@@ -345,6 +345,7 @@ Before sending a message to Kafka you can configure the
following headers.
|`CamelVertxKafkaMessageKey`| `VertxKafkaConstants.MESSAGE_KEY`|`String`|
Explicitly specify the message key, if partition ID is not specified, this will
trigger the messages to go into the same partition.
|`CamelVertxKafkaTopic`| `VertxKafkaConstants.TOPIC`|`String`| Explicitly
specify the topic to where produce the messages, this will be *preserved* in
case of header aggregation.
|`CamelVertxKafkaOverrideTopic`|
`VertxKafkaConstants.OVERRIDE_TOPIC`|`String`| Explicitly specify the topic to
where produce the messages, this will *not be preserved* in case of header
aggregation and it will take *precedence* over `CamelVertxKafkaTopic`.
+| `CamelVertxKafkaOverrideTimestamp` |
`VertxKafkaConstants.OVERRIDE_TIMESTAMP` | Long | The ProducerRecord also has
an associated timestamp. If the user did provide a timestamp, the producer will
stamp the record with the provided timestamp and the header is not preserved.
|=======================================================================
If you want to send a message to a dynamic topic then use
`VertxKafkaConstants.OVERRIDE_TOPIC` as its used as a one-time header
