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

ASF GitHub Bot commented on NIFI-2534:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/874

    Addressing issue when refresh Process Groups the user does not have READ 
access to

    NIFI-2534:
    - Refreshing using component IDs.
    - Code clean up.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-2534

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/874.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #874
    
----
commit 2b17318de2526c4bab82d525346213ee2b8f191d
Author: Matt Gilman <[email protected]>
Date:   2016-08-16T19:29:29Z

    NIFI-2534:
    - Refreshing using component IDs.
    - Code clean up.

----


> Error when stopping a process group the user doesn't have any permission for
> ----------------------------------------------------------------------------
>
>                 Key: NIFI-2534
>                 URL: https://issues.apache.org/jira/browse/NIFI-2534
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Bryan Bende
>            Assignee: Matt Gilman
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to