[jira] [Updated] (NIFI-16027) RPG status and status history return 404 when the RPG is in a connector canvas

["Mark Payne (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-16027:
------------------------------
    Status: Patch Available  (was: Open)

> RPG status and status history return 404 when the RPG is in a connector canvas
> ------------------------------------------------------------------------------
>
>                 Key: NIFI-16027
>                 URL: https://issues.apache.org/jira/browse/NIFI-16027
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When a Remote Process Group (RPG) lives inside a connector-managed canvas rather than the main NiFi flow, two API calls return 404:
>  * {{PUT /nifi-api/remote-process-groups/\{id}}} — the position update is persisted, but the response is a 404 because building the response entity fails
>  * {{GET /nifi-api/remote-process-groups/\{id}}} — the refresh call fails entirely
> Both failures come from the same root cause: {{ControllerFacade.getRemoteProcessGroupStatus()}} and {{getRemoteProcessGroupStatusHistory()}} locate the RPG by walking {{{}getRootGroup().findRemoteProcessGroup(id){}}}, which only searches the main flow hierarchy. When the RPG is in a connector canvas, this lookup returns null and a {{ResourceNotFoundException}} is thrown.
> The DAO layer ({{{}StandardRemoteProcessGroupDAO.locateRemoteProcessGroup{}}}) already searches connector-managed groups correctly, so the write operations succeed — only the status response path was missing the connector search.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)