[GitHub] aeaversa commented on issue #3281: NIFI-5986 Adding "Stop & Configure" button functionality to Processor…

[GitBox <gi...@apache.org>]

aeaversa commented on issue #3281: NIFI-5986 Adding "Stop & Configure" button functionality to Processor…
URL: https://github.com/apache/nifi/pull/3281#issuecomment-459339774
 
 
   @mcgilman - Thanks Matt!  So glad you got a chance to take a look. So, the motivation behind the change was purely to improve navigational efficiency and response time for end users in quickly being able to identify and correct a started processor that somehow had an incorrect configuration; limiting the amount of flow files that can traverse through the misconfigured processor. In working with both novice and advanced users of NiFi for the last year, I've had consistent requests that there be a simple button that allows a user to directly stop a processor and automatically allow editing of the processor's properties. The current navigational route from viewing a started processor's details (read only)  to editing its properties in the configure processor modal was always reported as a bit cumbersome: (ie - user clicks to open the  processor details modal of a started processor and notices a properties change is necessary > user clicks to close the processor details modal > user right/left clicks to stop the processor > user clicks to open what looks like the same processor details modal dialog, but now allows them to edit the desired properties).  I tried to keep the changes as simple as possible when I sent the PR. In this change, the processor details modal should  only present the "Stop & Configure" button when its launched directly from the canvas interface to limit any conflicts with  where it is used on other interfaces (ie: Summary, etc etc). ... as well it will disable the button if the processor is in any state other then RUNNING or the user demonstrates insufficient permissions. If there are other concerns you have, please let me know what those are and I can work to get those addressed. My thanks again for taking a look!
   
   Take care,
   
   --alex
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services