[
https://issues.apache.org/jira/browse/NIFI-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926937#comment-15926937
]
Eugene Hart commented on NIFI-3583:
-----------------------------------
Looks good. Someone else may need to determine whether it's ok to change the
logging level for "current behavior" from info to warn.
Thanks,
Gene
> PutFile should attempt to replace files atomically
> --------------------------------------------------
>
> Key: NIFI-3583
> URL: https://issues.apache.org/jira/browse/NIFI-3583
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.7.1, 1.1.1
> Environment: On Windows, NIO2's Files.move operation may not allow
> atomic file replacement, in which case it would have to fall back to the
> existing method.
> Reporter: Eugene Hart
> Assignee: Gray Gwizdz
> Priority: Trivial
>
> A PutFile configured with the "replace" conflict resolution strategy will
> first delete any existing file and then move the new temporary file into
> place. This causes there to be a small period of time where the file does not
> exist at all. This could cause problems with other processes relying on this
> file to always exist.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
