hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (MAPREDUCE-1319) Refactor ClientProtocol.getSystemDir usage on the job client side to instead use ClientProtocol.getStagingAreaDir
Date Mon, 21 Dec 2009 17:54:18 GMT

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

Devaraj Das reassigned MAPREDUCE-1319:
--------------------------------------

    Assignee: Devaraj Das

> Refactor ClientProtocol.getSystemDir usage on the job client side to instead use ClientProtocol.getStagingAreaDir
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1319
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1319
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.22.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>             Fix For: 0.22.0
>
>
> MAPREDUCE-181 introduced ClientProtocol.getStagingAreaDir. It'd be good to refactor the
client side where it infers the JobTracker's filesystem, etc. based on this. Seems like the
client needn't invoke ClientProtocol.getSystemDir at all.

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


Mime
View raw message