[
https://issues.apache.org/jira/browse/HADOOP-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-544:
---------------------------------
Attachment: id_wip1.patch
Bringing up this old issue, I am really uncomfortable with the ids handled as
strings. The attached patch is a proposal for the new XXXId classes that we may
use. I intend to continue the progress once we have grounded the need and the
design for this issue. Any thoughts ?
> Replace the job, tip and task ids with objects.
> -----------------------------------------------
>
> Key: HADOOP-544
> URL: https://issues.apache.org/jira/browse/HADOOP-544
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Attachments: id_wip1.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
