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

["Andre F de Miranda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963024#comment-15963024 ] 

Andre F de Miranda commented on NIFI-1131:
------------------------------------------

[~josephxsxn] I suspect [~joewitt] was referring to adding {{.displayName}} to the property builder allows you to discretionary change a property rendering value without causing impact to its underlying relationships (as within flow.xml)?

If so, all you need it to change your PR so that the property look a bit like this:

https://github.com/apache/nifi/blob/b7cdc6b382b09d601b1e9ecf81ef16b9246309b3/nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/ConsumeEWS.java#L161

> 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)