Github user taftster commented on the pull request:
https://github.com/apache/nifi/pull/80#issuecomment-137332775
I'm not sure that checking for the existence of an existing object is that
important. At minimum, it's causing an extra call to the remote S3 service to
determine if the object exists. The S3 service itself will not return a
different response code if the object previously existed.
What value is added by having the REL_NOT_FOUND relationship? What use
case is this trying to solve?
A request to delete an object, regardless of its previous existence, still
results in the same remote state. HTTP DELETE, being an idempotent method,
doesn't really care if the object existed beforehand or not.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
