You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Alexander Bukarev (JIRA)" <ji...@apache.org> on 2018/12/12 12:24:00 UTC
[jira] [Commented] (NIFI-3583) PutFile should attempt to replace
files atomically
[ https://issues.apache.org/jira/browse/NIFI-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718910#comment-16718910 ]
Alexander Bukarev commented on NIFI-3583:
-----------------------------------------
Hi everybody,
to my mind the issue is critical, is it possible to get it merged into the master branch?
> 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
> Attachments: 0001-NIFI-3853-PutFile-should-attempt-to-replace-files-at.patch
>
>
> 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
(v7.6.3#76005)