You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Tsuyoshi OZAWA (JIRA)" <ji...@apache.org> on 2014/02/13 22:01:21 UTC
[jira] [Commented] (TEZ-71) Remove references to stagingDir from
DAG App master
[ https://issues.apache.org/jira/browse/TEZ-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900726#comment-13900726 ]
Tsuyoshi OZAWA commented on TEZ-71:
-----------------------------------
These code base seems to have been moved to tez-mapreduce from DAGAppMaster and DAGImpl. Can we mark this JIRA as resolved?
> Remove references to stagingDir from DAG App master
> ---------------------------------------------------
>
> Key: TEZ-71
> URL: https://issues.apache.org/jira/browse/TEZ-71
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Labels: TEZ-0.3.0, TEZ-1, newbie
>
> In DAGImpl there is reference to stagingDir which has likely come in from MR. There should be no reason to have a dependency on some staging dir in the DAG AM.
> {code}
> String user =
> UserGroupInformation.getCurrentUser().getShortUserName();
> Path path = DAGApps.getStagingAreaDir(job.conf, user);
> if(LOG.isDebugEnabled()) {
> LOG.debug("startJobs: parent=" + path + " child=" + dagIdString);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)