You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flume.apache.org by "r2d2 (JIRA)" <ji...@apache.org> on 2018/06/04 02:52:00 UTC

[jira] [Updated] (FLUME-3238) TailDir Source + Kafka Sink + Memory Channel - Couldn't identify event source filename

     [ https://issues.apache.org/jira/browse/FLUME-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

r2d2 updated FLUME-3238:
------------------------
    Component/s: Kafka Channel

> TailDir Source + Kafka Sink + Memory Channel - Couldn't identify event source filename
> --------------------------------------------------------------------------------------
>
>                 Key: FLUME-3238
>                 URL: https://issues.apache.org/jira/browse/FLUME-3238
>             Project: Flume
>          Issue Type: Question
>          Components: Kafka Channel
>    Affects Versions: 1.8.0
>            Reporter: r2d2
>            Priority: Critical
>         Attachments: exmple1.log, exmple2.log, taildir_flume.conf.txt
>
>
> I am using Taildir to consume my log event and send it to kafka sink for further processing before its indexed to a table for any analytics.
> The events received in kafka topic doesn't carry which file the event belongs to and also couldn't trace back to the actual file the event really occurred.
> i tried so many config attribute as per the documentation, but the output doesnt change, it carries the raw event only to kafka topic.
> Did anyone had similar requirement and able to achieve it?
> As per the ticket# [https://issues.cloudera.org/browse/FLUME-258] they say its resolved. But doesnt seem to be available in new versions.
>  
> I have included my sample config and input files, if anyone tried similar implementation, please let me know how to achieve this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org