joewitt commented on pull request #5664: URL: https://github.com/apache/nifi/pull/5664#issuecomment-1018624053
The JIRA and code just describe what you want to do not the why. In your last comment it sounds like the why (a specific use case) is more clear. If I follow correctly you have a case whereby you have a service which looks at a specific file and you periodically want to update that file. And whenever you do update the file you'd like to have the previous file saved somewhere in case an operator might want to rollback. Makes perfect sense. Without this change how that would be well accomplished is a flow that simply writes a copy of the new dataset to the archive location using PutFile. Then using another PutFile writes a copy of it to the actual target location. You can modify names, replace, etc.. all as you wish. The full power/flexibility of the existing mechanisms are available to the user. They're not limited by what renaming options you exposed in PutFile, etc.. Additionally we didn't have to make substantial changes to a high use Processor and add a new set of properties to it. Do the existing capabilities not address the use case you've laid out or another use case you've not yet mentioned? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
