[jira] [Commented] (NIFI-14) Invoke HTTP Processor does not allow the sending certain NiFi paramaters as Http Headers

["Joe Skora (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623954#comment-14623954 ] 

Joe Skora commented on NIFI-14:
-------------------------------

I'd be interested in working on this, would the addition of these properties provide the greater control desired?
     * PROP_ATTRIBUTES_TO_EXCLUDE - regex of properties to suppress from headers.
     * PROP_ATTRIBUTE_LIST_TO_SEND - discrete list of properties to send.
     * PROP_ATTRIBUTE_LIST_TO_EXCLUDE - discrete list of properties to suppress from header.

I think the selection process would be as follows to give priority to lists over patterns and excludes over includes.
     1. Select attributes that match PROP_ATTRIBUTES_TO_SEND (existing behavior).
     2. Remove attributes that match PROP_ATTRIBUTES_TO_EXCLUDE.
     3. Add attributes in PROP_ATTRIBUTE_LIST_TO_SEND.
     3. Remove attributes in PROP_ATTRIBUTE_LIST_TO_EXCLUDE.

I do not think this should impact existing behavior.

> Invoke HTTP Processor does not allow the sending certain NiFi paramaters as Http Headers
> ----------------------------------------------------------------------------------------
>
>                 Key: NIFI-14
>                 URL: https://issues.apache.org/jira/browse/NIFI-14
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Joseph Witt
>            Priority: Minor
>
> Invoke HTTP should allow greater configuration options for controlling what does and does not get sent as HTTP Headers from flow file attributes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)