[ 
https://issues.apache.org/jira/browse/YARN-10897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andras Gyori updated YARN-10897:
--------------------------------
    Description: 
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).

  was:
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).


> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to