[
https://issues.apache.org/jira/browse/NIFI-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865581#comment-17865581
]
ASF subversion and git services commented on NIFI-13159:
--------------------------------------------------------
Commit 3c7b2626196c7e71f2c69495aea20fada9afc925 in nifi's branch
refs/heads/main from Michael W Moser
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3c7b262619 ]
NIFI-13159 Moved Remote Delete after Put for PutFTP/PutSFTP REPLACE Strategy
This closes #8914
Signed-off-by: David Handermann <[email protected]>
> Change how PutSFTP handles the REPLACE Conflict Resolution strategy
> -------------------------------------------------------------------
>
> Key: NIFI-13159
> URL: https://issues.apache.org/jira/browse/NIFI-13159
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Michael W Moser
> Assignee: Michael W Moser
> Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In the PutSFTP processor, in the specific case when "Dot Rename = true" and
> "Conflict Resolution = replace", PutSFTP currently behaves like this:
> * if remote filename.txt exists, delete it
> * send file to remote as .filename.txt
> * rename .filename.txt to filename.txt
> This causes filename.txt to not exist on the remote machine while the SFTP
> transfer is taking place. This is different than the PutFile processor,
> which will wait to replace the file until it has written the "dot file". Is
> it possible for PutSFTP to behave like this:
> * send file to remote as .filename.txt
> * if remote filename.txt exists, delete it
> * rename .filename.txt to filename.txt
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
