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

Hudson commented on FLUME-2955:
-------------------------------

UNSTABLE: Integrated in Flume-trunk-hbase-1 #183 (See 
[https://builds.apache.org/job/Flume-trunk-hbase-1/183/])
FLUME-2955. Add file path to the header in TaildirSource (mpercy: 
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=1ca0765aae795a41a43e39324f5f1c8bae57b751])
* 
flume-ng-sources/flume-taildir-source/src/test/java/org/apache/flume/source/taildir/TestTaildirSource.java
* 
flume-ng-sources/flume-taildir-source/src/main/java/org/apache/flume/source/taildir/ReliableTaildirEventReader.java
* 
flume-ng-sources/flume-taildir-source/src/main/java/org/apache/flume/source/taildir/TaildirSourceConfigurationConstants.java
* flume-ng-doc/sphinx/FlumeUserGuide.rst
* 
flume-ng-sources/flume-taildir-source/src/main/java/org/apache/flume/source/taildir/TaildirSource.java


> Add file path to the header in TaildirSource
> --------------------------------------------
>
>                 Key: FLUME-2955
>                 URL: https://issues.apache.org/jira/browse/FLUME-2955
>             Project: Flume
>          Issue Type: Improvement
>          Components: Sinks+Sources
>    Affects Versions: v1.7.0
>            Reporter: tinawenqiao
>            Assignee: tinawenqiao
>              Labels: file, path, taildirsource
>             Fix For: v1.7.0
>
>         Attachments: FLUME-2955.patch, FLUME-2955_2.patch, 
> FLUME-2955_3.patch, FLUME-2955_4.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> After using TaildirSource to collect log data, I found that there is no file 
> path in the flume event. 
> Though TaildirSource supports add customed header value like this : 
> a1.sources.r1.headers.f1.headerKey1 = value1, 
> we can't add file path to the header when the filegroup path contains regex 
> expression.File path is necessary to locate the log data.



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

Reply via email to