[
https://issues.apache.org/jira/browse/FLUME-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083359#comment-16083359
]
junjie SHI commented on FLUME-2960:
-----------------------------------
I think the cachePatternMatching mechanism has some problems, for example,
Agent.sources.static_log_source.filegroups = f1
Agent.sources.static_log_source.filegroups.f1.parentDir = / var / log / Bigdata
/ nodeagent /
Agent.sources.static_log_source.filegroups.f1.filePattern =. * / *. Log
When the taildir source is started, if I create a new file in the directory,
parentDir's modification time will not change, so taildir will not collect the
newly created file;
I do not know if this is a problem. This configuration can not use caching?
> 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: 1.7.0
> Reporter: tinawenqiao
> Assignee: tinawenqiao
> Labels: wildcards
> Fix For: 1.8.0
>
> Attachments: FLUME-2960_1.patch, FLUME-2960_2.patch,
> FLUME-2960_3.patch, FLUME-2960_4.patch, FLUME-2960_5.patch,
> FLUME-2960_6.patch, FLUME-2960_7.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.4.14#64029)
