You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2015/11/09 17:44:11 UTC

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

Joseph Percivall created NIFI-1131:
--------------------------------------

             Summary: 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
            Priority: Trivial


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.4#6332)