[
https://issues.apache.org/jira/browse/NIFI-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000994#comment-17000994
]
ASF subversion and git services commented on NIFI-6949:
-------------------------------------------------------
Commit 2277d08c8ec20101797a0642b629133d136bdfb1 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2277d08 ]
NIFI-6949: When a Controller Service is removed, ensure that any other service
that it references is obtained via the ControllerServiceProvider to ensure that
it is obtain to obtain and remove the reference, even if the service is in a
higher-level Process Group
Signed-off-by: Pierre Villard <[email protected]>
This closes #3933.
> When deleting a Controller Service, the references to higher-level Controller
> Services are not removed.
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6949
> URL: https://issues.apache.org/jira/browse/NIFI-6949
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Consider a flow where we have Process Group A. Group A has Controller Service
> A.
> Group A also has a child group, Group B. A Controller Service within Group B
> references Controller Service A.
> If said Controller Service is removed (or Group B removed), Controller
> Service A still holds the fact that the Controller Service was referencing
> it, even though the Controller Service no longer exists.
> To replicate:
> Create Process Group A. Within this group, create an AvroSchemaRegistry.
> Create Process Group B within Group A. Within Process Group B, create a
> JsonTreeReader and configure it to reference AvroSchemaRegistry. Now delete
> Process Group B. Configure Group A, then click to configure
> AvroSchemaRegistry. You'll see that the Controller Service still thinks
> JsonTreeReader is referencing it, even though the component doesn't exist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
