[
https://issues.apache.org/jira/browse/NIFI-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009724#comment-16009724
]
ASF GitHub Bot commented on NIFI-1131:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1583
@josephxsxn in light of Joe's comments, would you like to close this PR?
Cheers!
> InvokeHttp relationships don't match other processors
> -----------------------------------------------------
>
> Key: NIFI-1131
> URL: https://issues.apache.org/jira/browse/NIFI-1131
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Joseph Percivall
> Assignee: Joseph Niemiec
> Priority: Trivial
> Labels: newbie
>
> The current InvokeHttp relationships are "Original", "Response", "Retry", "No
> Retry" and "Failure". They should be renamed as such:
> "Original" -> "Success Request"
> "Response" -> stays same
> "Retry" -> "Retry Request"
> "No Retry" -> "No Retry Request"
> "Failure" -> "Failure Request"
> In other processors the "Original" relationship is the unmodified original
> flowfile but in InvokeHttp it is used as a destination for a modified
> request. In InvokeHttp the request flowfile coming in is routed to different
> relationships depending on the status code received and is modified with new
> attributes.
> This would be a breaking change and would be slated for 1.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
