From 95717437f33cbbbc7b1ebf6db23b286233f06ad4 Mon Sep 17 00:00:00 2001 From: Patrick Assuied Date: Thu, 21 Mar 2024 11:22:06 -0700 Subject: [PATCH] small tweak Signed-off-by: Patrick Assuied --- .../components-reference/supported-pubsub/setup-apache-kafka.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-apache-kafka.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-apache-kafka.md index be40629d3dd..fdeb4ed1955 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-apache-kafka.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-apache-kafka.md @@ -463,7 +463,7 @@ You can configure pub/sub to publish or consume data encoded using [Avro binary {{% alert title="Important" color="warning" %}} Currently, only message value serialization/deserialization is supported. Since cloud events are not supported, the `rawPayload=true` metadata must be passed when publishing Avro messages. -Please note that `rawPayload=true` should NOT be set for consumers as the message value, while properly deserialized into json will be wrapped into a CloudEvent. +Please note that `rawPayload=true` should NOT be set for consumers, as the message value will be wrapped into a CloudEvent and base64-encoded. Leaving `rawPayload` as default, will send the Avro-decoded message to the application. {{% /alert %}} When configuring the Kafka pub/sub component metadata, you must define: