[
https://issues.apache.org/jira/browse/NIFI-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579536#comment-14579536
]
Ricky Saltzer commented on NIFI-665:
------------------------------------
I see where you're coming from, and I do like your idea, but I think it's a
separate feature, as it's fits a different use case. That feature would make
sense to be added into the UpdateAttribute processor, as opposed to the
ExecuteProcess or ExecuteStreamProcess. Your suggestion is meant for assigning
attributes based on the output of a command, where as the feature I'm
suggesting is meant to assign any number of attributes during the course of
reading the stream of the flow file.
For instance, in the case of ExecuteStreamCommand, if I wanted to derive 20
attributes out of a moderate sized text file, it would require that I process
that file 20 times. If you give control to the application, you allow for more
efficient processing.
> 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)
