GitHub user tmgstevens opened a pull request:

    https://github.com/apache/flume/pull/105

    Flume 3046 - Kafak Sink and Source Configuration Improvements

    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.
    
    Adds configuration to Kafka Source to either disable the "topic" header, or 
at least configure it, and the same for the Kafka Sink,

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tmgstevens/flume FLUME-3046

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flume/pull/105.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #105
    
----
commit d849f5ab2db104e21d87795822d6d90bfedd3509
Author: Tristan Stevens <tris...@cloudera.com>
Date:   2016-04-05T08:33:43Z

    Merge remote-tracking branch 'apache/trunk' into trunk

commit 4c76b1709e92983c0b8b0c87a52363f78b75e1fa
Author: Tristan Stevens <tris...@cloudera.com>
Date:   2016-04-25T15:46:10Z

    Merge remote-tracking branch 'apache/trunk' into trunk

commit 1bb7b9acda688beecff83fd6a41ced083ba4506f
Author: Tristan Stevens <tris...@cloudera.com>
Date:   2017-01-23T21:19:35Z

    Merge remote-tracking branch 'apache/trunk' into trunk

commit 2ae3662cc1d6e841c5fc6a5819e5f6cd6aed3193
Author: Tristan Stevens <tris...@cloudera.com>
Date:   2017-01-23T21:24:33Z

    Changes for FLUME-3046 to introduce configuration to Kafka Source and Kafka 
Sink to avoid loopback effect due to 'topic' headers.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to