[ https://issues.apache.org/jira/browse/NIFI-7400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093755#comment-17093755 ]
Johan Cronsioe edited comment on NIFI-7400 at 4/27/20, 5:21 PM: ---------------------------------------------------------------- [~joewitt] Yes i agree with your suggestion. I was a bit fast to make a pull request but I'll instead look into changing the DistributeLoad processor. Edit: I saw that there is already a ticket for this functionality: https://issues.apache.org/jira/browse/NIFI-1675 so I think this ticket can be removed. was (Author: johancr): [~joewitt] Yes i agree with your suggestion. I was a bit fast to make a pull request but I'll instead look into changing the DistributeLoad processor. > Processor to route Flowfile when relationship is unavailable > ------------------------------------------------------------ > > Key: NIFI-7400 > URL: https://issues.apache.org/jira/browse/NIFI-7400 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions > Affects Versions: 1.12.0 > Reporter: Johan Cronsioe > Priority: Trivial > Labels: Processor > Original Estimate: 24h > Time Spent: 20m > Remaining Estimate: 23h 40m > > When a relationship becomes unavailable, it can be useful to route incoming > Flowfiles to an alternative relationship. As soon as the primary relationship > is available, Flowfiles will be routed to that relationship. > One scenario is when you want the most recent data to be sent to a > relationship, but if when that relationship is not available, the incoming > data is sent to an alternative relationship to be stored on disk until it can > be processed. -- This message was sent by Atlassian Jira (v8.3.4#803005)