[
https://issues.apache.org/jira/browse/FLUME-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163557#comment-16163557
]
ASF subversion and git services commented on FLUME-3046:
--------------------------------------------------------
Commit 54e2728a8e141ee63704018c4497bbe083c0f75f in flume's branch
refs/heads/trunk from [~tmgstev]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=54e2728 ]
FLUME-3046. Kafka Sink and Source Configuration Improvements
This patch fixes the infinite loop between Kafka source and Kafka sink
by introducing the following configuration parameters in those components:
- topicHeader in Kafka source to specify the name of the header where it
stores the topic name where the event comes from.
- setTopicHeader in Kafka source to control whether the topic name is stored
in the given header.
- topicHeader in Kafka sink to configure the name of the header which
is used to specify in which topic to send the event.
- allowTopicOverride in Kafka sink to control whether the target topic's name
can be overridden by the specified header.
This closes #105
Reviewers: Attila Simon
(Tristan Stevens via Denes Arvay)
> Kafka Sink and Source Configuration Improvements
> ------------------------------------------------
>
> Key: FLUME-3046
> URL: https://issues.apache.org/jira/browse/FLUME-3046
> Project: Flume
> Issue Type: Bug
> Affects Versions: 1.7.0
> Reporter: Jeff Holoman
> Assignee: Tristan Stevens
> Fix For: 1.9.0
>
>
> Currently the Kafka Source sets the header for the topic. The sink reads this
> value, rather than the statically defined topic value. We should fix this so
> that you can either change the topic header that is used, or just choose to
> prefer the statically defined topic in the sink.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
