mosermw commented on PR #7929: URL: https://github.com/apache/nifi/pull/7929#issuecomment-1781272173
I think the main motivation for requests like this are dataflow managers who don't want a separate UpdateAttribute processor creating a detailed notification message for each of the failure relationships. "If I have 10 FetchSFTP processors then I need 30 UpdateAttribute processors, when really I only want 1". At a large scale, little design decisions like this make a difference. I wonder what the community would think of consolidating the FetchSFTP "comms.failure", "not.found" and "permission.denied" relationships into 1 "failure" relationship and moving forward with an attribute that describes the failure reason? It would definitely be for NiFi 2.0 since it's a big breaking change. I suppose we would want @markap14 to weigh in on this as the original author. -- 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
