hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3147) Handle leaf queues with the same name properly
Date Mon, 28 Nov 2011 16:11:40 GMT

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

Ravi Prakash updated MAPREDUCE-3147:
------------------------------------

    Attachment: MAPREDUCE-3147.branch-0.23.patch

I just updated the patch to include a test and disallow two *Leaf* queues from having the
same name.

So that 
a->b->c
a->d->c
Would be illegal because (there are 2 queues named b) but 
a->b->c->d
a->b
Would be correct? I.e. Only leaf queues need be distinct.
                
> 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

        

Mime
View raw message