You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gray Gwizdz (JIRA)" <ji...@apache.org> on 2017/03/15 19:39:41 UTC

[jira] [Updated] (NIFI-3583) PutFile should attempt to replace files atomically

     [ https://issues.apache.org/jira/browse/NIFI-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gray Gwizdz updated NIFI-3583:
------------------------------
    Attachment: 0001-NIFI-3853-PutFile-should-attempt-to-replace-files-at.patch

Hi Eugene,

This seems like a great recommendation! Please see the attached patch which demonstrates the code fix that you have described.

Thanks!
Gray

> 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
>            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
(v6.3.15#6346)