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/22 20:22:09 UTC
[jira] Commented: (HADOOP-52) mapred input and output dirs must be
absolute
[ http://issues.apache.org/jira/browse/HADOOP-52?page=comments#action_12371451 ]
Doug Cutting commented on HADOOP-52:
------------------------------------
Overall this looks great! A few minor comments:
. your new local variables and non-static fields use underscores as word separators, rather than camelCase, as is both the Java convention and the convention used in the files you're changing. Can you please switch these to use camelCase?
. In LocalJobRunner there are potentially multiple threads changing the working directory of a single fs. Perhaps we should instead have a different fs instance for each job thread? Should we make FileSystem support clone()?
Thanks!
> 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
>
> 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