markobean commented on pull request #5664: URL: https://github.com/apache/nifi/pull/5664#issuecomment-1018666170
Your recommendation is exactly what we are currently performing. Specifically, writing the "new" file to a semi-permanent location prior to overwriting the existing file. So, the historical information is preserved, albeit prior to being "in use" by the controller service. Yet, this is perfectly adequate. The idea of incorporating the functionality into the PutFile processor itself is that it seemed a logical extension of the processor's capability. It seemed convenient to add the option to the processor especially since doing so is fully backward compatible with existing behavior. Also, it has the advantage of not duplicating data and archiving a copy if there was ever only a single file by that name, i.e. if there was no need for an archived copy. I'm still not clear on the words of caution you've brought up based on past experience. However, you are correct that a NiFi flow can be configured to accomplish nearly the same functionality. Also, it just occurred to me that performing this in a flow can result in archiving a file only once per cluster, but putting it in the processor itself means each node in the cluster would redundantly archive the file. -- 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
