slfan1989 commented on code in PR #4929:
URL: https://github.com/apache/hadoop/pull/4929#discussion_r1002292309


##########
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/dao/RMQueueAclInfo.java:
##########
@@ -25,9 +25,10 @@
 @XmlRootElement
 @XmlAccessorType(XmlAccessType.FIELD)
 public class RMQueueAclInfo {
-  protected boolean allowed;
-  protected String user;
-  protected String diagnostics;
+  private Boolean allowed;

Review Comment:
   Thank you very much for helping to review the code.
   
   If this field is `Boolean`, it is compatible with the original interface and 
can achieve accurate information in Federation mode.
   
   In Federation mode, we may have multiple SubClusters, and to verify whether 
the user has queue permissions, multiple results may be returned, and these 
results cannot be directly integrated.
   
   For example, we have 2 SubClusters (SC-1, SC-2), user jack wants to have 
access to the Default queue.
   Due to configuration reasons, jack has the `default` queue permission of 
`SC-1`, but does not have the queue permission of `SC-2`. If we call the router 
interface, we may get into difficulties. I don't know if jack has permission to 
access the default queue of the cluster. We cannot integrate information, but 
should return the SubCluster situation to the user separately, which is more 
reasonable.
   
   We define `FederationRMQueueAclInfo` extend `RMQueueAclInfo`, If we call the 
router's interface, we find that the return result is as follows:
   
   
![image](https://user-images.githubusercontent.com/55643692/197309576-2a7b4de4-343a-4da0-998f-8d54861e58b5.png)
   
   
   
   
   
   
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to