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

Peter Bacsko commented on YARN-9938:
------------------------------------

# Please address checkstyle issues (if they're addressabble, not like couple of 
weeks ago, when we decided to ignore those)
 # Add a minor comment to the catch clause to indicate that exception is OK

{noformat}
            try {
              testNestedUserQueueWithDynamicParentQueue(queueMappingsForUG, 
true, "h");
              fail("Leaf Queue 'h' doesn't exists");
            } catch (YarnException e) {
                // expected
            }
        
            try {
              testNestedUserQueueWithDynamicParentQueue(queueMappingsForUG, 
true, "a1");
              fail("Actual Parent Queue of Leaf Queue 'a1' is 'a', but as per 
queue "
                  + "mapping it returns primary queue as 'a1group'");
            } catch (YarnException e) {
                // expected
            }
{noformat}

> Validate Parent Queue for QueueMapping contains dynamic group as parent queue
> -----------------------------------------------------------------------------
>
>                 Key: YARN-9938
>                 URL: https://issues.apache.org/jira/browse/YARN-9938
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Manikandan R
>            Assignee: Manikandan R
>            Priority: Major
>         Attachments: YARN-9938.001.patch, YARN-9938.002.patch, 
> YARN-9938.003.patch, YARN-9938.004.patch
>
>
> Currently \{{UserGroupMappingPlacementRule#validateParentQueue}} validates 
> the parent queue using queue path. With dynamic group using %primary_group 
> and %secondary_group in place (Refer YARN-9841 and YARN-9865) , parent queue 
> validation should also happen for these above 2 queue mappings after 
> resolving the above wildcard pattern to corresponding groups at runtime.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to