The patch process has had problems identifying this patch because it has another Jira issue in the Synopsis line. I need to fix that limitation at some point...

On Jan 13, 2008, at 9:37 PM, Amareshwari Sri Ramadasu (JIRA) wrote:


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

Amareshwari Sri Ramadasu commented on HADOOP-2570:
--------------------------------------------------

+1 for Arun's patch

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: HADOOP-2570_1_20080112.patch, 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.


Reply via email to