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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 0.2.1
• Component/s: Core Framework
• Labels: logging
• Assignee: Unassigned
• Reporter: Dan Bress
• Created: 04/Aug/15 18:06
• Updated: 20/Jul/17 17:14
• Resolved: 20/Jul/17 17:14

Description

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.