You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Will McQueen (JIRA)" <ji...@apache.org> on 2012/06/17 02:13:42 UTC
[jira] [Commented] (FLUME-1284) Need host interceptor for hdfs
bucket path escape sequence
[ https://issues.apache.org/jira/browse/FLUME-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393411#comment-13393411 ]
Will McQueen commented on FLUME-1284:
-------------------------------------
Note that I attached the patch to this ticket because I'm unable to publish a ReviewBoard ticket... says "server error".
> Need host interceptor for hdfs bucket path escape sequence
> ----------------------------------------------------------
>
> Key: FLUME-1284
> URL: https://issues.apache.org/jira/browse/FLUME-1284
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.2.0
> Environment: RHEL 6.2 64-bit
> Reporter: Will McQueen
> Assignee: Will McQueen
> Fix For: v1.2.0
>
> Attachments: FLUME-1284.patch
>
>
> The Flume NG docs specify that %{host} can be used in the HDFS bucket path. This means that the 'host' header must exist within a Flume event. But Flume events don't have it by default. So some users (including myself) have resorted to writing a custom interceptor that adds it.
> It would be beneficial to have a built-in HostInterceptor that adds a 'host' header to all events passing through that interceptor. The interceptor should have properties that allow an existing 'host' header's value to be preserved, and that allow to choose between including the hostname or host IP for the 'host' header value.
> The built-in HostInterceptor would serve the same purpose as the built-in TimestampInterceptor, which is to allow all bucket path escape sequences specified in the docs to be used without each user needing to write their own custom interceptor for this common case.
--
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