Jeff Lord created FLUME-2138:
--------------------------------
Summary: Setting hdfs.useLocalTimeStamp = true without the
timestamp interceptor configured will result in delivery failure
Key: FLUME-2138
URL: https://issues.apache.org/jira/browse/FLUME-2138
Project: Flume
Issue Type: Bug
Affects Versions: v1.3.1
Reporter: Jeff Lord
hdfs.useLocalTimeStamp = true
in my config file, but the following error occurs in hdfs sink:
013-07-29 11:09:56,923 (lifecycleSupervisor-1-0) [INFO -
org.apache.flume.instrumentation.MonitoredCounterGroup.register(MonitoredCounterGroup.java:110)]
Monitoried counter group for type: SINK, name: hdfsSink, registered
successfully.
2013-07-29 11:09:56,923 (lifecycleSupervisor-1-0) [INFO -
org.apache.flume.instrumentation.MonitoredCounterGroup.start(MonitoredCounterGroup.java:94)]
Component type: SINK, name: hdfsSink started
2013-07-29 11:09:56,925 (SinkRunner-PollingRunner-DefaultSinkProcessor) [DEBUG
- org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:143)] Polling
sink runner starting
2013-07-29 11:09:56,929 (SinkRunner-PollingRunner-DefaultSinkProcessor) [ERROR
- org.apache.flume.sink.hdfs.HDFSEventSink.process(HDFSEventSink.java:422)]
process failed
java.lang.NullPointerException: Expected timestamp in the Flume event headers,
but it was null
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)
at
org.apache.flume.formatter.output.BucketPath.replaceShorthand(BucketPath.java:200)
at
org.apache.flume.formatter.output.BucketPath.escapeString(BucketPath.java:396)
at org.apache.flume.sink.hdfs.HDFSEventSink.process(HDFSEventSink.java:356)
at
org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:68)
at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
at java.lang.Thread.run(Thread.java:662)
2013-07-29 11:09:56,931 (SinkRunner-PollingRunner-DefaultSinkProcessor) [ERROR
- org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:160)] Unable to
deliver event. Exception follows.
--
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
