[
https://issues.apache.org/jira/browse/MINIFI-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947445#comment-15947445
]
Andrew Christianson commented on MINIFI-239:
--------------------------------------------
[~aldrin] You're right. I think 248 was created without awareness of this
ticket. We could close it as redundant. Or, possibly, we might want those other
processors to improve compatibility with flows exported from NiFi.
Is there an ETA on when Invoke might be available? Want to avoid development
collision as much as possible.
> Create a C++ HTTP client processor to match the InvokeHTTP processor
> --------------------------------------------------------------------
>
> Key: MINIFI-239
> URL: https://issues.apache.org/jira/browse/MINIFI-239
> Project: Apache NiFi MiNiFi
> Issue Type: Task
> Components: C++, Extensions
> Reporter: Andrew Grande
> Assignee: marco polo
>
> There is a ListenHTTP processor, but nothing for the client side (e.g. to
> invoke REST APIs). The civetweb library is already being used, can be
> leveraged to implement the InvokeHTTP parity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
