[
https://issues.apache.org/jira/browse/NIFI-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579479#comment-14579479
]
Ryan Blue commented on NIFI-665:
--------------------------------
I can understand wanting to do this, but I don't think it is a good idea
defining a file format or injecting an environment variable where the
attributes data should go. That just doesn't sound reliable. I think it is
reasonable to go with an approach where you get to set a property with the
output of a command. Maybe even do that a few times in a processor to cut down
on the size of the graph, like the route processor does: You define a property
and a command, then that command is run on the flow file, which gets updated
with the property name as the attribute and the command output as the value.
> Design method for attaching attributes using
> ExecuteProcess/ExecuteStreamCommand
> --------------------------------------------------------------------------------
>
> Key: NIFI-665
> URL: https://issues.apache.org/jira/browse/NIFI-665
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Ricky Saltzer
> Assignee: Ricky Saltzer
> Attachments: NIFI-665.file-based.patch, sample-script.sh
>
>
> Currently, the ExecuteProcess and ExecuteStreamCommand processors can only
> consume and produce new flow files. Although they can access attributes
> attached to the flow files through the use of environment variables, they
> have no way to update or attach new attributes.
> I think it could be really useful if there was a generic way for us to attach
> flow file attributes using these two processors. Since environment variables
> created or updated by a flow file are only visible to the executing process,
> we'll unfortunately not be able to utilize it.
> The purpose of this JIRA is to provide a forum for how we could potentially
> solve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
