[
https://issues.apache.org/jira/browse/FLUME-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690804#comment-15690804
]
Jason Kushmaul commented on FLUME-2994:
---------------------------------------
[~liorze], Patch #3 addresses the failing tests.
[~bessbd], I have not directly addressed your concern. Someone would have to
write a test function to create N files and verify the uniqueness of every
file's "getInode()" result. I may do that yet.
[~kamleshpandey], I have not addressed your finding but intuition makes me
think this is logging framework issue, not flume. It's up to the logging
framework to close the file and rotate to a new filename I would think. I am
going to run 1.7 with this patch on windows but not with same logging framework
or configuration.
> flume-taildir-source: support for windows
> -----------------------------------------
>
> Key: FLUME-2994
> URL: https://issues.apache.org/jira/browse/FLUME-2994
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources, Windows
> Affects Versions: v1.7.0
> Reporter: Jason Kushmaul
> Assignee: Jason Kushmaul
> Priority: Trivial
> Fix For: v1.8.0
>
> Attachments: FLUME-2994-3.patch, taildir-mac.conf, taildir-win8.1.conf
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The current implementation of flume-taildir-source does not support windows.
> The only reason for this from what I can see is a simple call to
> Files.getAttribute(file.toPath(), "unix:ino");
> I've tested an equivalent for windows (which of course does not work on
> non-windows). With an OS switch we should be able to identify a file
> independent of file name on either system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
