Matt Gilman created NIFI-5208:

             Summary: Editing a flow on a Disconnected Node
                 Key: NIFI-5208
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework, Core UI
            Reporter: Matt Gilman
            Assignee: Matt Gilman

Currently, editing on a flow on a disconnected node is allowed. This feature is 
useful when needing to debug a node-specific environmental issue prior to 
re-joining the cluster. However, this can also lead to issues when the user 
doesn't realize that the node they are viewing is disconnected. This was never 
an issue in our 0.x baseline as viewing the disconnected node required the user 
to manually direct their browser away from the NCM and towards the disconnected 

In 1.x, this can happen transparently with the need for the user to redirect 
their browser. There is a label at the top to indicate that the node is 
disconnected but this is not sufficient. If the user continues to with their 
edits, it will make it difficult to re-join the cluster without manual 
inventions to retain their changes.

There is a dialog that should inform the user that the cluster connection state 
has changed. However, there appears to be a regression that is preventing that 
dialog from showing. We should restore this dialog and make it confirm the 
users intent to make changes in a disconnected state.

This message was sent by Atlassian JIRA

Reply via email to