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 Witt (JIRA)" <ji...@apache.org> on 2015/11/07 04:30:11 UTC

[jira] [Updated] (NIFI-1009) InvokeHTTP should be able to be scheduled without any incoming connection for GET operations

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

Joseph Witt updated NIFI-1009:
------------------------------
    Fix Version/s:     (was: 0.4.0)

> InvokeHTTP should be able to be scheduled without any incoming connection for GET operations
> --------------------------------------------------------------------------------------------
>
>                 Key: NIFI-1009
>                 URL: https://issues.apache.org/jira/browse/NIFI-1009
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mark Payne
>
> Many users have been confused by InvokeHTTP not running when it is a "Source" processor. It probably doesn't make sense to do a POST or a PUT operation without an incoming FlowFile. However, if the Processor is configured to do a GET or DELETE, it should be able to run as a Source processor.
> Validation logic should indicate that the processor is not valid if it has no incoming connection and is configured to perform a POST or a PUT.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)