You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/03/23 19:42:21 UTC
[jira] Resolved: (HADOOP-52) mapred input and output dirs must be
absolute
[ http://issues.apache.org/jira/browse/HADOOP-52?page=all ]
Doug Cutting resolved HADOOP-52:
--------------------------------
Resolution: Fixed
I have committed this. Thanks for adding unit tests! I had to add a Thread.sleep(1000) to the dfs test code before the tests would pass, to give the datanode a chance to introduce itself to the namenode before the client code started using the fs. Perhaps this is just masking a bug. Perhaps DFSClient should sleep and retry when NameNode.create() throws an exception?
> mapred input and output dirs must be absolute
> ---------------------------------------------
>
> Key: HADOOP-52
> URL: http://issues.apache.org/jira/browse/HADOOP-52
> Project: Hadoop
> Type: Bug
> Components: mapred
> Versions: 0.1
> Reporter: Doug Cutting
> Assignee: Owen O'Malley
> Fix For: 0.1
> Attachments: cwd.patch, cwd2.patch, cwd3.patch
>
> DFS converts relative pathnames to be under /user/$USER. But MapReduce jobs may be submitted by a different user than is running the jobtracker and tasktracker. Thus relative paths must be resolved before a job is submitted, so that only absolute paths are seen on the job tracker and tasktracker. I think the simplest way to fix this is to make JobConf.setInputDir(), setOutputDir(), etc. resolve relative pathnames.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira