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 98ec8582575c0a1ecb832a2f00e61e9ac7068c87 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Oct 30 08:13:11 2020 +0100 CAMEL-15770 - Fixed docs about kafkaHeaderSerializer --- components/camel-kafka/src/main/docs/kafka-component.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/components/camel-kafka/src/main/docs/kafka-component.adoc b/components/camel-kafka/src/main/docs/kafka-component.adoc index eced7a3..18542c1 100644 --- a/components/camel-kafka/src/main/docs/kafka-component.adoc +++ b/components/camel-kafka/src/main/docs/kafka-component.adoc @@ -562,11 +562,11 @@ Since kafka headers allows only `byte[]` values, in order camel exchnage header 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. -In order to override default functionality uri parameters can be set: `headerDeserializer` for `from` route and `kafkaHeaderSerializer` for `to` route. Example: +In order to override default functionality uri parameters can be set: `headerDeserializer` for `from` route and `headerSerializer` for `to` route. Example: ``` from("kafka:my_topic?headerDeserializer=#myDeserializer") ... -.to("kafka:my_topic?kafkaHeaderSerializer=#mySerializer") +.to("kafka:my_topic?headerSerializer=#mySerializer") ``` By default all headers are being filtered by `KafkaHeaderFilterStrategy`.
