From cfc35e09bf2be8d49d714cb99cb9618ca894df95 Mon Sep 17 00:00:00 2001 From: Roland Johann Date: Tue, 11 Oct 2016 15:36:12 +0200 Subject: [PATCH] dded note to documentation declaring what header fields the kafka source will set and which kind of impacts that implicit behaviour can have. --- flume-ng-doc/sphinx/FlumeUserGuide.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/flume-ng-doc/sphinx/FlumeUserGuide.rst b/flume-ng-doc/sphinx/FlumeUserGuide.rst index cd76bb35cd..f1a2d962c6 100644 --- a/flume-ng-doc/sphinx/FlumeUserGuide.rst +++ b/flume-ng-doc/sphinx/FlumeUserGuide.rst @@ -1286,6 +1286,10 @@ Other Kafka Consumer Properties -- These properties are used to co The Kafka Source also provides defaults for the key.deserializer(org.apache.kafka.common.serialization.StringSerializer) and value.deserializer(org.apache.kafka.common.serialization.ByteArraySerializer). Modification of these parameters is not recommended. +.. note:: The Kafka Source sets several event headers if they don't exist already: "timestamp", "topic", "partition" and "key" (if it's a keyed kafka message). + Especially the header field "topic" can lead to unexpected behaviour when used in combination with the Kafka Sink. + This header field overwrites the destination topic of the sinks configuration and leads to an indefinite loop producing the messages to into the topic where they has been read from. + Deprecated Properties =============================== =================== =============================================================================================