[ 
https://issues.apache.org/jira/browse/MAPREDUCE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746014#action_12746014
 ] 

Tom White commented on MAPREDUCE-777:
-------------------------------------

I think we can support the use case Todd mentioned above with a relatively 
small change (and without resorting to aspects). Change the JobClient 
constructors to static factory methods:

{code}
public JobClient() { ... }

public JobClient(Configuration conf) throws IOException { ... }
{code}

becomes

{code}
public static JobClient get() { ... }

public static JobClient get(Configuration conf) throws IOException { ... }
{code}

Then at a later point we can change the implementation of the static methods to 
return a custom implementation of JobClient, without having to change 
JobClient's 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: patch-777-1.txt, patch-777-2.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.

Reply via email to