You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Gergely Pollák (Jira)" <ji...@apache.org> on 2021/09/21 14:09:00 UTC

[jira] [Commented] (YARN-10897) Introduce QueuePath class

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

Gergely Pollák commented on YARN-10897:
---------------------------------------

[~gandras] thank you for the patch, LGTM+1, merged to trunk.

> Introduce QueuePath class
> -------------------------
>
>                 Key: YARN-10897
>                 URL: https://issues.apache.org/jira/browse/YARN-10897
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager, yarn
>            Reporter: Andras Gyori
>            Assignee: Andras Gyori
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> The same idioms regarding queue path strings are repeated over and over in the codebase. Including but not limited to:
> * Get parent queue of a queue path
> * Split queue path and iterate through it
> * Traverse a queue path all the way to root
> It also inherently provides some kind of type safety and documentation extension to the code (eg. instead of Map<String, Object> the Map<QueuePath, Object> communicates more clearly what we group items by).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org