[jira] [Resolved] (NIFI-806) Starting an invalid processor has different behavior if processor is selected or not

["Pierre Villard (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-806.
---------------------------------
    Resolution: Cannot Reproduce

> Starting an invalid processor has different behavior if processor is selected or not
> ------------------------------------------------------------------------------------
>
>                 Key: NIFI-806
>                 URL: https://issues.apache.org/jira/browse/NIFI-806
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.2.1
>            Reporter: Dan Bress
>            Priority: Minor
>              Labels: logging
>
> The behavior of how the application reports problems with a processor in the log is slightly different depending on whether or not you have a processor selected when you hit the "start" button.
> Steps to reproduce
> 1) drag an update attribute
> 2) set "success" to auto terminate
> 3) drag a new update attribute
> 4) click on the graph such that no processors are selected
> 5) press "start" in the toolbar
> 6) observe in nifi-app.log an exception stack trace is printed
> 7) press stop
> 8) select both processors
> 9) press "start" in the toolbar
> 10) observe in nifi-app.log there is no stack trace
> Not sure which behavior is correct.  Generally the app leans towards not printing stack traces, so I might vote to follow that precedent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)