[
https://issues.apache.org/jira/browse/NIFI-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079569#comment-17079569
]
ASF subversion and git services commented on NIFI-7087:
-------------------------------------------------------
Commit 84968e70d293e49888addc3870c6a9cf222103b0 in nifi's branch
refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=84968e7 ]
NIFI-7087: Use FlowManager.findAllConnections() when available
Signed-off-by: Matthew Burgess <[email protected]>
This closes #4026
> Framework should use FlowManager.findAllConnections() when available
> --------------------------------------------------------------------
>
> Key: NIFI-7087
> URL: https://issues.apache.org/jira/browse/NIFI-7087
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Many places in the framework the entire list of Connections is needed, and
> sometimes the list is assembled by recursively collecting all the Connections
> for each child process group. This can be an expensive operation, especially
> since FlowManager keeps a Set of all Connections. It is noticeable in
> ConnectionStatusAnalytics for example.
> Whenever a FlowManager object is available to a class that retrieves all
> Connections, it should use FlowManager.findAllConnections() rather than
> rootGroup.findAllConnections().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
