[
https://issues.apache.org/jira/browse/HADOOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557906#action_12557906
]
Arun C Murthy commented on HADOOP-2570:
---------------------------------------
bq. the 2 places where jobcache dir was used in streaming was to 'chmod' the
executable and to lookup this directory in PATH. Would be it OK to construct
jobCacheDir as done in HADOOP-2227 ?
Lohit, that still won't help scripts which use "../work/<myscript>" - so this
is the best approach for 0.15.3.
In light of this bug HADOOP-2116 is a little more complicated than originally
thought, I have a few thoughts about this which I'll put up there.
bq. Submiting the patch with symlinks to ../work from taskdir
+1
> 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
> Priority: Blocker
> Fix For: 0.15.3
>
> Attachments: patch-2570.txt
>
>
> 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.
