[
https://issues.apache.org/jira/browse/FLUME-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931796#comment-13931796
]
Otis Gospodnetic commented on FLUME-2344:
-----------------------------------------
Should Fix Version field here in JIRA be set to 1.5.0?
Should this code be marked as Experimental?
I think that's the practice for new Flume code, and it would be good if this
could go in Flume 1.5.0 so it can get some real-life testing.
Regardless of where the code came from, shouldn't that test be
platform-agnostic? I think if you run the test under Windows now it just won't
work because of those /tmp/.... files.
One more, separate question:
Should this really live in Flume? Logically speaking, shouldn't the core
tailing functionality be separate and independent of Flume? And then shouldn't
Flume have something like "NativeTailSource" that makes use of this tailing
project/logic?
> New source for tailing files
> ----------------------------
>
> Key: FLUME-2344
> URL: https://issues.apache.org/jira/browse/FLUME-2344
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Environment: Centos 6.4, Java 1.6.0_34
> Reporter: Guillermo Ortiz Fernández, Pragsis.
> Fix For: v1.4.0
>
> Attachments: FLUME-2344-0.patch
>
>
> New source to be able to tail a file. There's a extra file when it saves the
> last offset until it has been read. So, it Flume is down, it could read the
> data it lost. It has been implemented control about rotated files.
> The possible variables to configure this source are:
> -BufferSize gives us the possibility to send little to little.
> -Separator to cut the lines wherever we want to to generate our events.
> -WatchedFile to indicate what file we want to watch.
> -RotatedFile to indicate where the wacthed file is going to rotate.
> -Type of events to indicate if we generate one event per line or we want to
> group many lines and just emit one event.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
