You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "George Knaggs (Jira)" <ji...@apache.org> on 2021/07/29 15:25:00 UTC
[jira] [Commented] (NIFI-7588) InvokeHTTP ignoring custom
parameters when stop+finalize+start
[ https://issues.apache.org/jira/browse/NIFI-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389966#comment-17389966 ]
George Knaggs commented on NIFI-7588:
-------------------------------------
This bug happened to me, and we are on 1.13.2, and what a pain it was to identify the issue was a bug and not an issue at the rest endpoint. At first everything is working fine, then like Alejandro described, you stop the processor and then out of lack of patience you choose to Terminate the running tasks, and from that point on it stops working. The headers set with "Attributes to Send" or as dynamic properties, stop being sent as headers. I tried the workarounds suggested above, but only after creating a new processor resolved the issue.
> InvokeHTTP ignoring custom parameters when stop+finalize+start
> --------------------------------------------------------------
>
> Key: NIFI-7588
> URL: https://issues.apache.org/jira/browse/NIFI-7588
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.11.4
> Environment: Amazon Linux
> Reporter: Alejandro Fiel Martínez
> Priority: Major
> Attachments: invokeHTTP_NiFi_bug.png
>
>
> I have an InvokeHTTP processor, with 3 custom paramenters to be passed as headers, If I add an SSL Context Service and remove it, the processor stop using those 3 paramenters and I have to delete and recreate then, they are there, but I see in DEBUG that there are not used in the GET request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)