[
https://issues.apache.org/jira/browse/FLUME-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393941#comment-15393941
]
Attila Simon commented on FLUME-2960:
-------------------------------------
Only a minor correction that you actually turned off caching when taildirsource
is configured with wildcards instead of making cache work with wildcard dirs.
It is fine by me, please see my code review.
Given this hype around monitoring file system for changes, I think we might
want to re-explore
https://docs.oracle.com/javase/tutorial/essential/io/notification.html. With
that service this request would have been much simpler also the caching
wouldn't be needed any more. Unfortunately I recall that [~mpercy] mentioned
some malfunctioning about that service. Mike do you remember the details of
your concern what should one look for when evaluating the usability of this
feature?
> Support Wildcards in directory name in TaildirSource
> ----------------------------------------------------
>
> Key: FLUME-2960
> URL: https://issues.apache.org/jira/browse/FLUME-2960
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.7.0
> Reporter: tinawenqiao
> Assignee: tinawenqiao
> Labels: wildcards
> Fix For: v1.7.0
>
> Attachments: FLUME-2960_1.patch, FLUME-2960_2.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> In our log management project, we wan't to track many log files like this:
> /app/dir1/log.*
> /app/dir2/log.*
> ...
> /app/dirn/log.*
> But TaildirSource can't support wildcards in filegroup directory name. The
> following config is expected:
> a1.sources.r1.filegroups.fg = /app/\*/log.*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
