[
https://issues.apache.org/jira/browse/NIFI-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579292#comment-14579292
]
Ryan Blue commented on NIFI-665:
--------------------------------
[~rickysaltzer], can you outline the use case for this a little more clearly?
What is the value of setting attributes like this?
Also, what about making an option to set the output of the command as a single
attribute? That would support use cases like running inspection utilities, like
{{avro-tools schema <file>}} and capturing the output without the complexity of
producing a special format in the command or injecting a property that the
script knows about. This goes back to the use case you're thinking of and
whether it fits with this alternative way of doing things.
> 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)
