This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch camel-2.x
in repository https://gitbox.apache.org/repos/asf/camel.git
commit b54f2a6cb1c9c45a53f9de36f9854b2b9fdf9faf
Author: Ahmed <42283870+amd...@users.noreply.github.com>
AuthorDate: Sat Jul 30 11:25:54 2022 +0200
Fix typo in kafka-component.adoc
exchange instead of exchnage
---
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 ac5d4bdd16d..3f15d89028d 100644
--- a/components/camel-kafka/src/main/docs/kafka-component.adoc
+++ b/components/camel-kafka/src/main/docs/kafka-component.adoc
@@ -594,7 +594,7 @@ on the `KafkaComponent` that creates instances of your
custom implementation.
When consuming messages from Kafka, headers will be propagated to camel
exchange headers automatically.
Producing flow backed by same behaviour - camel headers of particular exchange
will be propagated to kafka message headers.
-Since kafka headers allows only `byte[]` values, in order camel exchnage
header to be propagated its value should be serialized to `bytes[]`,
+Since kafka headers allows only `byte[]` values, in order camel exchange
header to be propagated its value should be serialized to `bytes[]`,
otherwise header will be skipped.
Following header value types are supported: `String`, `Integer`, `Long`,
`Double`, `Boolean`, `byte[]`.
Note: all headers propagated *from* kafka *to* camel exchange will contain
`byte[]` value by default.
