[HADOOP-544] Replace the job, tip and task ids with objects.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.18.0
• Fix Version/s: 0.18.0
• Hadoop Flags: Incompatible change, Reviewed

Release Note

Introduced new classes JobID, TaskID and TaskAttemptID, which should be used instead of their string counterparts. Deprecated functions in JobClient, TaskReport, RunningJob, jobcontrol.Job and TaskCompletionEvent that use string arguments. Applications can use xxxID.toString() and xxxID.forName() methods to convert/restore objects to/from strings.

• Assignee: Enis Soztutar
• Reporter: Owen O'Malley
• Created: 19/Sep/06 05:47
• Updated: 08/Jul/09 16:51
• Resolved: 30/Apr/08 12:23

Description

I think that it is silly to have tools parsing the strings that the framework builds for task ids. I propose:

class JobId implements Writable {
public int getJobId()

{...}

}

class TaskId implements Writable {
public JobId getJobId();
public boolean isMap()

{ ... }
public int getTaskId() { ... }

}

class TaskAttemptId implements Writable {
public TaskId getTaskId();
public int getAttemptId();
}

each of the classes will have a toString() method that generates the current string.