[
https://issues.apache.org/jira/browse/MAPREDUCE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755124#action_12755124
]
Owen O'Malley commented on MAPREDUCE-777:
-----------------------------------------
.bq As far as possible we shouldn't expose old interfaces through the new ones
(e.g. ClusterStatus, JobStatus, TaskReport) etc. in ClientProtocol, Cluster
etc. I'm still debating if we should deprecate JobStatus/TaskReport and replace
them with newer ones in org.apache.hadoop.mapreduce and making the old ones
derive from the new ones. Maybe it's beyond the scope of this jira
We can't expose the old classes in the new API. In particular, it is critical
that we can have clients just use the new API with no references to the mapred
package. To do that, as Arun says, we need to move the functionality into the
new API and have the old API extended the new classes. (And be deprecated) I
think that has to be in the scope of this jira since this is the jira that is
adding them to the new API.
> A method for finding and tracking jobs from the new API
> -------------------------------------------------------
>
> Key: MAPREDUCE-777
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-777
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: client
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.21.0
>
> Attachments: m-777.patch, patch-777-1.txt, patch-777-2.txt,
> patch-777-3.txt, patch-777-4.txt, patch-777-5.txt, patch-777-6.txt,
> patch-777-7.txt, patch-777-8.txt, patch-777.txt
>
>
> We need to create a replacement interface for the JobClient API in the new
> interface. In particular, the user needs to be able to query and track jobs
> that were launched by other processes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
