[ 
https://issues.apache.org/jira/browse/FLUME-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725365#comment-14725365
 ] 

ASF GitHub Bot commented on FLUME-2781:
---------------------------------------

GitHub user gherreros opened a pull request:

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

    FLUME-2781 proposed implementation

    Implemented a tiny change so putting to the channel is consistent with 
take, so if parseAsFlumeEvent is false it uses the event body text instead of 
an Avro Flume event object.

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

    $ git pull https://github.com/gherreros/flume trunk

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

    https://github.com/apache/flume/pull/24.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 #24
    
----
commit 2c02cfa484460056ec4d040dc2ec568e19fa916b
Author: gherreros <[email protected]>
Date:   2015-09-01T13:07:55Z

    FLUME-2781 When the Kafka channel is configured as
    parseAsFlumeEvent=false, any writes to the topic are done as plain text
    (so the events can be read correctly)

----


> A Kafka Channel defined as parseAsFlumeEvent=false cannot be correctly used 
> by a Flume source
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLUME-2781
>                 URL: https://issues.apache.org/jira/browse/FLUME-2781
>             Project: Flume
>          Issue Type: Improvement
>            Reporter: Gonzalo Herreros
>
> When a Kafka channel is configured as parseAsFlumeEvent=false, the channel 
> will read events from the topic as text instead of serialized Avro Flume 
> events.
> This is useful so Flume can read from an existing Kafka topic, where other 
> Kafka clients publish as text.
> However, if you use a Flume source on that channel, it will still write the 
> events as Avro so it will create an inconsistency and those events will fail 
> to be read correctly.
> Also, this would allow a Flume source to write to a Kafka channel and any 
> Kafka subscriber to listen to Flume events passing through without binary 
> dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to