[
https://issues.apache.org/jira/browse/FLUME-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224609#comment-13224609
]
Arvind Prabhakar commented on FLUME-986:
----------------------------------------
@Ralph - there is substantial interest within the community for trunk
implementation as is evident from the IRC discussions as well as occasional
user/dev list emails. While the current set of active committers may not be
looking at these sources, I am sure that there are people working on it.
On the other hand, if there is indeed no development on these issues, even then
we cannot close them unless there is a clear way by which they can be addressed
by 1.x. Once we have feature parity on 1.x with 0.9.x we can start a discussion
if it makes sense to retain the open issues from the past or not. Until then
closing these issues does not make sense to me.
> Refresh functionality doesn't work for tailDir on Flume OG
> ----------------------------------------------------------
>
> Key: FLUME-986
> URL: https://issues.apache.org/jira/browse/FLUME-986
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.4
> Reporter: Kathleen Ting
>
> The refresh functionality doesn't work as intended for tailDir on Flume OG
> (must resort to restarting flume nodes when configuration changes are made).
> The issue manifests in DirWatcher.java where we want to refresh the agents
> but they report a dir doesn't exist, which could happen on a corrupted hash
> file.
--
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
