markobean commented on pull request #5664: URL: https://github.com/apache/nifi/pull/5664#issuecomment-1018543213
The option of changing the filename is not applicable to the use case in mind. Suppose a PutFile is writing an updated file used by a Controller Service. The Controller Service will reload the file when a change is detected, but it requires the filename to remain the same. Therefore, changing the filename upon PutFile failure and trying again is not possible in this scenario. Also, in the above use case, it is desirable to save (archive) the current file before replacing it. The archived file can be used as a fallback if the new file is corrupt or otherwise unusable. The archive also can provide a historical record of when a certain configuration changed. I'm not sure I follow the "error prone and too limiting". The rules as laid out seem pretty straight-forward. Can you further explain the concern or historical errors that occurred? Thanks. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
