NIFI-14777 Restore capability from NiFi 1.x to view upstream/downstre… - #11582
NIFI-14777 Restore capability from NiFi 1.x to view upstream/downstre…#11582markobean wants to merge 2 commits into
Conversation
…am connections. View connections > upstream/downstream is available in the context menu from a variety of components: input/output ports, processors, process groups, remote process groups and funnels.
|
I tested the functionality of this and it looks good. The pop up window shows accurate connections and the buttons redirect to the appropriate component. I would suggest using different Icons for the context menu options so that the arrows are pointing up and down, to correspond with "Upstream" and "Downstream". Maybe slanted up/down arrows? Just a thought. |
Thanks @Freedom9339. I updated the arrows, as suggested. The upstream context menu item shows an arrow pointing up and to the left, and downstream shows down and to the right. It's slightly more intuitive and looks good. |
…am connections. View connections > upstream/downstream is available in the context menu from a variety of components: input/output ports, processors, process groups, remote process groups and funnels.
Summary
In NiFi 1.x, there was a context menu option for View Connections > upstream/downstream. This is available from any component, but it is particularly useful for input/output ports. The reason is that the connections to ports are not visible on the graph at the same level as the ports themselves. The user must go to the parent process group, and then there is ambiguity which connections are connected to which ports in cases where there are multiple connections and ports on the process group.
A key feature of the View Connections table is that each item in the table is clickable and will navigate to the selected component or connection.
Restoring this feature makes it far easier to navigate the graph and identify complex routing/connectivity issues in the flow.
NIFI-14777
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking
Pull Request Tracking
NIFI-00000NIFI-00000VerifiedstatusPull Request Formatting
mainbranchVerification
Verification was performed by interacting with the graph and testing a variety of scenarios including:
Build
./mvnw clean install -P contrib-checkLicensing
LICENSEandNOTICEfilesDocumentation