[
https://issues.apache.org/jira/browse/MINIFICPP-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Bakai updated MINIFICPP-965:
-----------------------------------
Description:
Only the Success relationship is added as a supported one, only Success,
RelRetry and RelNoRetry are used, RelFailure and RelResponse are unused.
We should decide what error relationships we need and use them properly. Also,
currently both the original FlowFile and response FlowFile are routed to
Success, which is hard to use, and inconsistent with NiFi. Response FlowFiles
should be routed to RelResponse.
There might be other unfinished features/deviation from documentation in
InvokeHTTP as well.
was:
Only the Success relationship is added as a supported one, only Success,
RelRetry and RelNoRetry are used, RelFailure and RelResponse are unused.
We should decide what error relationships we need and use them properly. Also,
currently both the original FlowFile and response FlowFile are routed to
Success, which is hard to use, and inconsistent with NiFi. Response FlowFiles
should be routed to RelResponse.
There might be other unfinished features/deviation from documentation in
ListenHTTP as well.
> InvokeHTTP's relationships are unfinished/illogical
> ---------------------------------------------------
>
> Key: MINIFICPP-965
> URL: https://issues.apache.org/jira/browse/MINIFICPP-965
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Daniel Bakai
> Priority: Major
>
> Only the Success relationship is added as a supported one, only Success,
> RelRetry and RelNoRetry are used, RelFailure and RelResponse are unused.
> We should decide what error relationships we need and use them properly.
> Also, currently both the original FlowFile and response FlowFile are routed
> to Success, which is hard to use, and inconsistent with NiFi. Response
> FlowFiles should be routed to RelResponse.
> There might be other unfinished features/deviation from documentation in
> InvokeHTTP as well.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)