[ https://issues.apache.org/jira/browse/NIFI-11105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681147#comment-17681147 ]
ASF subversion and git services commented on NIFI-11105: -------------------------------------------------------- Commit d9f35b89741ff2cd13ad77b7a8f995c96bac36b7 in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d9f35b8974 ] NIFI-11105: This closes #6895. When mapping Parameter Context to VersionedParameterContext, don't bother mapping those that have already been mapped, as it is redundant Signed-off-by: Joe Witt <joew...@apache.org> > Download Flow takes long time when there are many Process Groups with > Parameter Contexts > ---------------------------------------------------------------------------------------- > > Key: NIFI-11105 > URL: https://issues.apache.org/jira/browse/NIFI-11105 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Reporter: Mark Payne > Assignee: Mark Payne > Priority: Major > Fix For: 1.20.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When we export a flow for download, we have to serialize any referenced > Parameter Context as part of the JSON. To do this, we build up a collection > of VersionedParameterContexts. The logic that we use does this for every > Process Group. So if we have many small Process Groups, each bound to a > Parameter Context, we formulate that VersionedParameterContext every time. > However, there is no need to create more than one VersionedParameterContext > for each existing ParameterContext. This mapping becomes very expensive and > can take many minutes for flows that contain lots of Parameters and lots of > Process Groups. -- This message was sent by Atlassian Jira (v8.20.10#820010)