[
https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150985#comment-13150985
]
Nathan Roberts commented on MAPREDUCE-3147:
-------------------------------------------
What I would like to avoid is one subtree limiting the namespace of another.
One of the selling points behind the hierarchical queue structure is that an
owner of a subtree can manage that subtree independently of the others. If the
leaves of the tree are required to have globally unique names, it doesn't seem
like we're quite meeting that goal (my subtree can't add a queue called
"default", if someone else has already taken that name). Is there no way we can
maintain compatibility AND get to independent namespaces? Could we support the
concept of an alias whereby relative queue names can be linked into the
hierarchy "d->root.a.b.c.d"?
> 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
