hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Bhandarkar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2570) streaming jobs fail after HADOOP-2227
Date Thu, 10 Jan 2008 17:23:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557707#action_12557707

Milind Bhandarkar commented on HADOOP-2570:

If this issue goes into 0.15.3, then we should do what Arun proposed, IMO.

In 0.16, when HADOOP-2116 is committed, the scripts will have job.local.dir config variable
(exposed as an env var job_local_dir to streaming).

> streaming jobs fail after HADOOP-2227
> -------------------------------------
>                 Key: HADOOP-2570
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2570
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/streaming
>    Affects Versions: 0.15.2
>            Reporter: lohit vijayarenu
>            Assignee: Amareshwari Sri Ramadasu
>             Fix For: 0.15.3
> HADOOP-2227 changes jobCacheDir. In streaming, jobCacheDir was constructed like this
> {code}
> File jobCacheDir = new File(currentDir.getParentFile().getParent(), "work");
> {code}
> We should change this to get it working. Referring to the changes made in HADOOP-2227,
I see that the APIs used in there to construct the path are not public. And hard coding the
path in streaming does not look good. thought?

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

View raw message