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

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

Github user mcgilman commented on the issue:

    https://github.com/apache/nifi/pull/698
  
    Yeah, I'm unable to replicate. The first message you mentioned sounds like 
the request was attempted like it was prior to the fix. Maybe your browser had 
some old JS cached. The "Must be authorized..." message is a client side check 
that I added to address NIFI-2242. Let me know if you still seeing any 
weirdness.


> UI does not render components properly if moving multiple components with 
> mixed permissions
> -------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2242
>                 URL: https://issues.apache.org/jira/browse/NIFI-2242
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Mark Payne
>            Assignee: Matt Gilman
>             Fix For: 1.0.0
>
>
> I selected several processors and connections (a small, disconnected graph) 
> and dragged the components to the right. When I released, I got an error 
> message because I didn't have 'write' permissions to one of the processors. 
> All of the other processors moved, but he one processor did not. As a result, 
> the connections were also not refreshed properly and were not connecting the 
> components visually. Clicking 'refresh' on the graph did cause the 
> connections to be redrawn properly.
> This could be addressed in two different ways. First, we could simply refresh 
> the canvas in this case.
> Secondly, we could use a Flow Snippet to move the components, in which case 
> none of the components would be moved if the user attempted this action 
> because the user does not have sufficient permissions for all components.



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

Reply via email to