[jira] [Comment Edited] (NIFI-9779) Stop PG causing accidentally stop other RPG where locate at other PG

["YIM SIO KEK (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-9779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503373#comment-17503373 ] 

YIM SIO KEK edited comment on NIFI-9779 at 3/9/22, 8:30 AM:
------------------------------------------------------------

[~Chris S] sure. glad to hear this had address and resolved. One more thing I observed at the 'Flow Configuration History' didn't capture the Stop PG1 record and only captured the RPG Stopped event. Not sure this had fixed in NIFI 9684

!image-2022-03-09-16-27-55-659.png|width=863,height=193!


was (Author: JIRAUSER286314):
[~Chris S] sure. glad to hear this had address and resolved 

> Stop PG causing accidentally stop other RPG where locate at other PG
> --------------------------------------------------------------------
>
>                 Key: NIFI-9779
>                 URL: https://issues.apache.org/jira/browse/NIFI-9779
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.15.2, 1.15.3
>            Reporter: YIM SIO KEK
>            Priority: Major
>         Attachments: image-2022-03-09-16-27-55-659.png
>
>
> To Reproduce:
>  # Create two PG name as PG1 and PG2 at root level
>  # At PG1, simply drag one generateflowfile (set to 600s) connect to a funnel then start it
>  # At PG2, simply drag a RPG and fill up the URL then enable it
>  # Back to root level UI, click on PG1 and stop PG1
>  # You will observe the RPG will disable accidently in PG2
>  # Further check at 'Flow Configuration History' you will see the details of bug
> Workaround
>  # Stop processors inside PG instead of outside



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