Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-9684

Starting a PG starts RPGs in sibling PGs as well

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.16.0
    • None
    • None

    Description

      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.

      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.

      Solution

      Send the id of the selected process group

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tpalfy Tamas Palfy
            tpalfy Tamas Palfy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 40m
                40m

                Slack

                  Issue deployment