Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-13159

Change how PutSFTP handles the REPLACE Conflict Resolution strategy

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: In Progress
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • Extensions
    • None

    Description

      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

       

      Attachments

        Issue Links

          Activity

            People

              mosermw Michael W Moser
              mosermw Michael W Moser
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10m
                  10m