Nicholas Carenza created NIFI-3464:
--------------------------------------
Summary: Claim Lock on Flowfile modifications
Key: NIFI-3464
URL: https://issues.apache.org/jira/browse/NIFI-3464
Project: Apache NiFi
Issue Type: Improvement
Reporter: Nicholas Carenza
Priority: Minor
Attachments: operate-lock.png
I am getting ready to introduce Nifi to my team and opening up the UI to them.
One thing that concerns me is the chance that two of us might try to edit the
same processor or related processors while the other is working on it.
It would be nice if there was a way to indicate in the UI to other clients that
you are going to modify a certain processor/processor group or the entire flow.
This might be an enforced lock or just a warning/suggestion for other users. I
imagine just having a button on the screen, maybe in the Operate window since
it already switches context based on your selection (see image attachment).
It's probably enough to implement a lock as a warning. It will visually
indicate if someone has locked it and warn if you try to change it anyways. you
don't even need to keep track of who locked it and any user could perform the
unlock. A more advanced implementation might add lock/unlock access privileges.
For me, it would be enough to communicate intention to modify a particular
processor or group through the UI.
One scenario I image is: some downstream processor starts failing, buffers
start filling, errors start logging, slack starts putting and more than one
person notice and attempt to triage.
Then of course there are actual locking mechanisms with which come a lot more
complications.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
