[
https://issues.apache.org/jira/browse/FLUME-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273726#comment-13273726
]
E. Sammer commented on FLUME-1197:
----------------------------------
I can see making the header configurable (although I still don't like it) but
I'd prefer not to make it flume.timestamp by default. The "system provided"
headers should simply be unqualified. Those that use custom headers should use
their own qualified namespace.
> Use of "timestamp" Header is hardcoded and not configurable
> -----------------------------------------------------------
>
> Key: FLUME-1197
> URL: https://issues.apache.org/jira/browse/FLUME-1197
> Project: Flume
> Issue Type: Improvement
> Reporter: Arvind Prabhakar
>
> Currently the HDFS sink uses the "timestamp" header to resolve the
> destination file path. The Syslog sources inject this header into the events
> for such downstream use.
> This enhancement request to change this functionality such that:
> * The header name is configurable and defaults to "flume.timestamp" to reduce
> collision with application namespace
> * The system still works with "timestamp" header to preserve backward
> compatibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
