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

Xi Fang commented on HADOOP-9790:
---------------------------------

Thanks, [~daryn]. I am sorry. I didn't make the description clear. Attached is 
the stderr information. Basically TestDistCpActionExecutor calls DistCp in some 
mapreduceJob. A minicluster is launched for executing this. However, the 
jobToken file can't be found when the mapred job is running. See the error: 

file:/"D:/git/Monarch/project/oozie-monarch/core/target/test-data/minicluster/mapred/local/0_0/taskTracker/test/jobcache/job_20130725105336682_0001/jobToken"
    

The cause of this is the surrounding quotes around the path.  As I mentioned in 
my previous comment, on Windows when setting up environment variable for child 
tasks, we add quotes to the environment variable values to avoid escaping 
special characters. In Cmd shell, the quotation marks are set as part of the 
environment variable value. So when we receive the environment variables in 
Hadoop code, we should remove the surrounding quotes.   

Please let me know if you have any concerns or questions.
                
> Job token path is not unquoted properly
> ---------------------------------------
>
>                 Key: HADOOP-9790
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9790
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1-win
>         Environment: Windows
>            Reporter: Xi Fang
>            Assignee: Xi Fang
>         Attachments: HADOOP-9790.1.patch, stderr.txt
>
>
> Found during oozie unit tests (TestDistCpActionExecutor) and oozie ad-hoc 
> testing (distcp action).
> The error is:
> Exception reading 
> file:/"D:/git/Monarch/project/oozie-monarch/core/target/test-data/minicluster/mapred/local/0_0/taskTracker/test/jobcache/job_20130725105336682_0001/jobToken".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to