[
https://issues.apache.org/jira/browse/NIFI-16338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18114681#comment-18114681
]
ASF subversion and git services commented on NIFI-16338:
--------------------------------------------------------
Commit 9dadf04ce02c7c57a921c338d4fc23bfe23216d1 in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9dadf04ce02 ]
NIFI-16338 - Resolve ancestor controller service references during Connector
component verification
This closes #11672
> Resolve ancestor controller service references during Connector component
> verification
> --------------------------------------------------------------------------------------
>
> Key: NIFI-16338
> URL: https://issues.apache.org/jira/browse/NIFI-16338
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Connector component verification creates temporary contexts from versioned
> component properties. During this process, StandardComponentContextProvider
> translates versioned controller service identifiers to runtime instance
> identifiers.
> The current implementation builds this mapping using
> ProcessGroup.findAllControllerServices(), which searches the current process
> group and its descendants. This does not match controller service visibility
> rules: a processor or controller service can reference services in its
> current process group or ancestor groups, but not descendant groups.
> As a result, Connector verification can fail when a component in a nested
> process group references a controller service defined in a parent group. The
> versioned identifier remains unresolved and validation reports that it is not
> a valid controller service identifier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
