[jira] [Resolved] (NIFI-1131) InvokeHttp relationships don't match other processors

["David Handermann (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann resolved NIFI-1131.
------------------------------------
    Resolution: Won't Fix

> 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: Joe Percivall
>            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
(v8.20.1#820001)