You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Gabor Gyimesi (Jira)" <ji...@apache.org> on 2021/04/26 15:35:01 UTC

[jira] [Assigned] (MINIFICPP-1494) InvokeHTTP should behave in the same way as NiFi

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

Gabor Gyimesi reassigned MINIFICPP-1494:
----------------------------------------

    Assignee: Gabor Gyimesi

> InvokeHTTP should behave in the same way as NiFi
> ------------------------------------------------
>
>                 Key: MINIFICPP-1494
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1494
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Ferenc Gerlits
>            Assignee: Gabor Gyimesi
>            Priority: Minor
>
> There are some differences between the NiFi and MiNiFi implementations of InvokeHTTP.  I suspect these are not intentional, and we should change MiNiFi to behave in the same way as NiFi.
>  #  When InvokeHTTP is timer-driven and the Method is GET, then NiFi does not require an incoming flow file, but MiNiFi does.
>  # The NiFi version of InvokeHTTP has an output relationship called Original.  This is called Success in MiNiFi; it should probably be renamed to Original.
> TODO: any others?
> *These changes could break some existing flows; discuss whether this is acceptable.*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)