[
https://issues.apache.org/jira/browse/NIFI-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348692#comment-14348692
]
Mark Payne commented on NIFI-380:
---------------------------------
Joe,
ExecuteStreamCommand captures up to the first 4000 characters from the error
stream and puts it as a FlowFile attribute. We should consider doing the same
thing. Ideally, we would then start capturing again after we create the first
flowfile and capture up to the next 4000 characters for the next FlowFile and
so on.
If you have some other idea for what to do with it, go for it.
You're right about the ping - it seemed like a good idea at the time :)
> Create ExecuteProcess processor
> -------------------------------
>
> Key: NIFI-380
> URL: https://issues.apache.org/jira/browse/NIFI-380
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Attachments:
> 0002-NIFI-380-Initial-import-of-ExecuteProcess-processor.patch,
> 0003-NIFI-380-Added-documentation.patch
>
>
> this processor should behave similar to ExecuteStreamCommand but is a source
> processor, rather than taking in flowfiles. Also, it needs to support the
> ability to periodically transfer a FlowFile with the output of the command,
> even if the command has not finished, and then create a new FlowFile
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
