[
https://issues.apache.org/jira/browse/NIFI-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867115#comment-15867115
]
ASF GitHub Bot commented on NIFI-3183:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/1363
@pvillard31 I could envision someone configuring the flow really
wanting/needing to control whether these new attributes you've created are
placed onto the flow file. if the command contained sensitive information or
details they'd not want made available downstream for example. That said this
could be removed with an UpdateAttribute and perhaps we can save this for a
later PR/JIRA if necessary. Will continue the review.
> Add "command" and "arguments" attributes to FlowFiles generated by
> ExecuteProcess and ExecuteStreamCommand
> ----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3183
> URL: https://issues.apache.org/jira/browse/NIFI-3183
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Randy Gelhausen
> Assignee: Pierre Villard
>
> It's common to use ExecuteProcess/ExecuteStreamCommand to generate new data
> sources which are routed and handled downstream dynamically based on the
> command executed (and arguments passed).
> Adding the given command and arguments as attributes of FlowFiles generated
> by these processors makes this pattern easier to implement.
> See MiNiFi-161/MiNiFi-166 for additional detail.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
