hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-4419) JobTracker.setJobPriority() doesn't check for a jobID lookup failing
Date Fri, 07 Nov 2008 02:18:44 GMT

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

Chris Douglas resolved HADOOP-4419.

    Resolution: Duplicate

This is being fixed in HADOOP-4420

> JobTracker.setJobPriority() doesn't check for a jobID lookup failing
> --------------------------------------------------------------------
>                 Key: HADOOP-4419
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4419
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0, 0.20.0
>            Reporter: Steve Loughran
>            Priority: Minor
> Looking at the entry points of the JobTracker API, it seems that JobTracker.setJobPriority()
 doesnt expect the JobID lookup ever to return null
> It goes straight from lookup to checking access, an operation that assumes that job!=null
>     JobInProgress job = jobs.get(jobid);
>     checkAccess(job, QueueManager.QueueOperation.ADMINISTER_JOBS);
> Recommend: add a test that calls this operaton with an invalid jobID, then fix the code
as appropriate

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message