[
https://issues.apache.org/jira/browse/NIFI-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406720#comment-15406720
]
ASF GitHub Bot commented on NIFI-1876:
--------------------------------------
Github user jtstorck commented on the issue:
https://github.com/apache/nifi/pull/694
After doing some investigation, I saw that the FlowMerger wasn't merging
labels or funnels, it was just picking the first instance of the component from
each node. I added the use of the mergers for labels and funnels to the
FlowMerger and tested on a three-node cluster, and the merging looks good now.
With one node denying the read permissions on labels and funnels, the UI is
correctly disabling them. Ready for review.
> Clustering - Merge all responses based on authorization
> -------------------------------------------------------
>
> Key: NIFI-1876
> URL: https://issues.apache.org/jira/browse/NIFI-1876
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Each node in a cluster may have a different view of the authorization access
> policies simply to in the timing of updates. Because of this, all requests
> need to be merged accordingly.
> Requests are directed at a specific resource. These would result in some 403
> responses.
> Some requests are contain a filtered view of a number of resources. These
> would need to be updated to return the most restrictive set of responses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
