[
https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164000#comment-13164000
]
Hudson commented on MAPREDUCE-3147:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #1374 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1374/])
MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi
Prakash via mahadev)
mahadev :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1211243
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java
> Handle leaf queues with the same name properly
> ----------------------------------------------
>
> Key: MAPREDUCE-3147
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3147.branch-0.23.patch,
> MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch,
> MAPREDUCE-3147.branch-0.23.patch
>
>
> If there are two leaf queues with the same name, there is ambiguity while
> submitting jobs, displaying queue info. When such ambiguity exists, the
> system should ask for clarification / show disambiguated information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
