[
https://issues.apache.org/jira/browse/NIFI-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286665#comment-17286665
]
Nissim Shiman commented on NIFI-8233:
-------------------------------------
[~pvillard] You are correct. Your suggestion would work.
I was thinking of making ListenHTTP more in sync with how it receives other
data (i.e. when "Send as FlowFile" set to false in PostHTTP),
where there is finer control already built in regarding which attributes we
want to accept, without the nifi graph user needing to use a follow on
UpdateAttribute,
but you are correct in that your solution will allow this to work as is.
> ListenHTTP - add ability to filter out incoming flowfile attributes
> -------------------------------------------------------------------
>
> Key: NIFI-8233
> URL: https://issues.apache.org/jira/browse/NIFI-8233
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Major
>
> Currently ListenHTTP handles incoming attributes with the property:
> "HTTP Headers to receive as Attributes (Regex)"
> This works except for the case where the data is from PostHTTP and was sent
> as a flowfile.
> In this scenerio the flowfile attributes are not sent as headers, rather the
> flowfile contents and attributes are packaged together and sent to ListenHTTP
> and there is no option for the ListenHTTP processor to do any attribute
> filtering.
> The property:
> "Flowfile attributes to be filtered (Regex)"
> will be added to handle this case as part of this ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
