You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/11/05 12:32:33 UTC

[jira] [Resolved] (FLUME-1123) flume output bucketing

     [ https://issues.apache.org/jira/browse/FLUME-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashish Paliwal resolved FLUME-1123.
-----------------------------------
       Resolution: Won't Fix
    Fix Version/s: v0.9.5

Won't fix. 0.X branch not maintained anymore

> flume output bucketing
> ----------------------
>
>                 Key: FLUME-1123
>                 URL: https://issues.apache.org/jira/browse/FLUME-1123
>             Project: Flume
>          Issue Type: Bug
>          Components: Configuration, Sinks+Sources
>    Affects Versions: v0.9.3
>            Reporter: Nguyen
>             Fix For: v0.9.5
>
>
> Hi all,
> Could you please help me to understand why flume can't control the output of log-events to particular directories based on the value of event's field. Example:
> collectorSink("hdfs://namenode/flume/webdata/%H00/", "%{host}-")
> 1. a flume collector receives a message to be logged to hdfs with source is SyslogTcp and Sink is HDFS 2. 16:00 PM Flume process crashes --> SyslogNG buffers the log-events on the local disk 3. 19:00 PM Flume process restart --> SyslogNG sends the buffered-data to flume. It means log-events have a delay 4. I expect that Flume controls the output of log-events to particular directories based on the value of event's field , it means log-events on 16:00 PM will be created on the directory /flume/webdata/1600 5. The result is that directory /webdata/1900 is created for log-events 
> Could you please tell me why flume cannot control the output of log-events as described in docu?
> Thank you



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