[
https://issues.apache.org/jira/browse/FLUME-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588999#comment-13588999
]
Hudson commented on FLUME-1922:
-------------------------------
Integrated in flume-trunk #362 (See
[https://builds.apache.org/job/flume-trunk/362/])
FLUME-1922. HDFS Sink should optionally insert the timestamp at the sink.
(Revision 6293146224a261d340b39824ce7dadcda9b1efd7)
Result = SUCCESS
mpercy :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=6293146224a261d340b39824ce7dadcda9b1efd7
Files :
*
flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/TestHDFSEventSink.java
* flume-ng-core/src/main/java/org/apache/flume/formatter/output/BucketPath.java
*
flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/HDFSEventSink.java
*
flume-ng-core/src/test/java/org/apache/flume/formatter/output/TestBucketPath.java
* flume-ng-doc/sphinx/FlumeUserGuide.rst
> HDFS Sink should optionally insert the timestamp at the sink
> ------------------------------------------------------------
>
> Key: FLUME-1922
> URL: https://issues.apache.org/jira/browse/FLUME-1922
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: v1.4.0
>
> Attachments: FLUME-1922-1.patch, FLUME-1922.patch
>
>
> The HDFS Sink currently looks for the timestamp in the event headers. If some
> events are delayed then the events will end up in the old directory itself.
> We should allow the HDFS Sink to use the local timestamp to decide where the
> event goes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
