You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2022/02/15 19:56:00 UTC

[jira] [Assigned] (NIFI-9684) Starting a PG starts RPGs in sibling PGs as well

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

Mark Payne reassigned NIFI-9684:
--------------------------------

    Assignee: Tamas Palfy

> Starting a PG starts RPGs in sibling PGs as well
> ------------------------------------------------
>
>                 Key: NIFI-9684
>                 URL: https://issues.apache.org/jira/browse/NIFI-9684
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Tamas Palfy
>            Assignee: Tamas Palfy
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> h3. Issue
> https://issues.apache.org/jira/browse/NIFI-7788 introduced the change that whenever a user starts an entire process group, all remote process groups within get transmission enabled.
> This works properly if the user is within the process group and issues a start by right-clicking on the canvas.
> However if the user does does this by right-clicking on the process group (while being in its parent group), all remote process groups start transmitting within the parent process group. This issue is also true when stopping the process group.
> h3. Root cause
> The 2 cases (right clicking on the canvas vs on the process group) is handled differently in _nf-actions.js_. When doing the latter the id of the parent of the selected process group (aka. the current active process group) is sent via the REST interface.
> h3. Solution
> Send the id of the selected process group



--
This message was sent by Atlassian Jira
(v8.20.1#820001)