[
https://issues.apache.org/jira/browse/NIFI-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926952#comment-15926952
]
Eugene Hart commented on NIFI-3583:
-----------------------------------
I'd lean towards info since that's what it uses currently for the same
behavior. Also, if it has to delete first (windows) it will probably have to do
that everytime and it would probably just be noise in the logs.
> 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
(v6.3.15#6346)
