[
https://issues.apache.org/jira/browse/NIFI-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045240#comment-18045240
]
Joe Witt commented on NIFI-15345:
---------------------------------
The user can tell it not to do temp renaming. It is an extremely long held
common practice/idiom in goofy file transport land to write files with dot
naming then rename (remove the dot) once finished. However, in some systems
this is not necessary or desirable. Set the property "Dot Rename" to false and
you should be fine. I don't know for sure how the gaining system will know for
certain the file is completely written but ... yolo.
> PutSFTP fails for servers that automatically move the file immediately after
> upload
> -----------------------------------------------------------------------------------
>
> Key: NIFI-15345
> URL: https://issues.apache.org/jira/browse/NIFI-15345
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.6.0, 2.7.0, 2.7.1
> Reporter: Paul Kelly
> Priority: Major
> Labels: SFTP
>
> Since NIFI-14720, NiFi now calls .stat() on the uploaded file after the
> upload completes. For SFTP servers that are configured to automatically move
> a file immediately after the upload completes, this move can happen fast
> enough that NiFi's stat call throws an error because the file no longer
> exists. This error causes NiFi to fail with "Failed to transfer content to
> [remote_file_name]", and to transfer the flowfile to the failure
> relationship, even though the file was successfully uploaded.
> The stat call should be moved to its own try/catch block away from the
> upload, in order to handle those errors separately. Ideally stat should only
> be called if any attributes are going to be set, or it should be configurable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
