[ https://issues.apache.org/jira/browse/NIFI-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586943#comment-15586943 ]
ASF GitHub Bot commented on NIFI-2905: -------------------------------------- Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/1143 Built with `contrib-check` and verified all tests pass. I started the application, and used an `ExecuteProcess` processor with command `cd` and arguments `non-existent-dir`. With `Redirect Error Stream` set to **false** (default), the errors appeared as bulletins. With `Redirect Error Stream` set to **true**, no bulletins were raised, and the error message was found in the resulting flowfile contents. +1, merging. > ExecuteProcess should log error stream instead of ignoring it > ------------------------------------------------------------- > > Key: NIFI-2905 > URL: https://issues.apache.org/jira/browse/NIFI-2905 > Project: Apache NiFi > Issue Type: Bug > Reporter: Koji Kawamura > Assignee: Koji Kawamura > > When a command executed by ExecuteProcess processor didn't work properly and > emitted error messages to error stream, but the processor's configured with > 'Redirect Error Stream' as 'false' (default), then the error messages are > ignored, thus there's no way for user to see what went wrong. > It can provide better UX by logging error stream as WARN level so that user > can see it on bulletin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)