[
https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150866#comment-13150866
]
Ravi Prakash commented on MAPREDUCE-3147:
-----------------------------------------
Arun!
At the very least we should prevent leaf queues from having the same name. So
if there are two queues configured
root.a.b.c.d and
root.x.y.z.d
Then there is no way for a user to submit their job to a.b.c.d. (Currently the
lookup table is overwritten with the last parsed queue name)
Can you please explain why this would be an incompatible change? Were
multi-level hierarchical queues supported before? If they were, then this would
be an incompatible change. However if they were not, the first level of queues
would have the same name as always.
> 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
>
>
> 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
