You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Bean (Jira)" <ji...@apache.org> on 2023/08/10 13:54:00 UTC
[jira] [Assigned] (NIFI-11934) InvokeHTTP does not send filename attribute
[ https://issues.apache.org/jira/browse/NIFI-11934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Bean reassigned NIFI-11934:
--------------------------------
Assignee: Mark Bean
> InvokeHTTP does not send filename attribute
> -------------------------------------------
>
> Key: NIFI-11934
> URL: https://issues.apache.org/jira/browse/NIFI-11934
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.23.0
> Reporter: Mark Bean
> Assignee: Mark Bean
> Priority: Major
>
> The InvokeHTTP processor can be configured to send FlowFile attributes when using the POST HTTP method. Certain attributes are excluded from being sent. These include some core attributes: UUID, FILENAME and PATH. It makes sense to exclude UUID and PATH as these will be created/assigned when the FlowFile is received by a ListenHTTP processor. However, filename should be allowed to remain as the original filename.
> Not only is does this make good sense from a flow perspective, but it is also consistent with the behavior of the now-deprecated PostHTTP processor. This functionality must be maintained or dataflows will break when PostHTTP is no longer available.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)