[
https://issues.apache.org/jira/browse/NIFI-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348186#comment-14348186
]
Joseph Witt commented on NIFI-380:
----------------------------------
mark
Two findings:
1) the reading of the error stream was going to never never land. This was
problematic because one of the commands I tested with wrote all of its output
to the error stream. I have some mods i'll commit tomorrow/today which let the
user decide whether to redirect error stream to the input stream. If false
then it will read/dump anything to the error stream but never hold it in mem.
2) The use of ping is likely not portable. For instance on linux the test ran
indefinitely. I've modifed the test to use 'echo testprocess' which should
work based on what I've read for windows/linux/ and mac osx.
Will commit this morning or so to a branch for you to review.
Thanks
joe
> 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)
