[ http://issues.apache.org/jira/browse/HADOOP-673?page=comments#action_12450942 ] Owen O'Malley commented on HADOOP-673: --------------------------------------
Richard, I don't understand why having the jar expanded in ".." is unacceptable to you. It seems to me the requirements are: 1. there be an easy way to get to the expanded jar 2. each task run in sandbox In previous systems we've taken this approach and it has worked very well. The problem with links is that they are not supported in Java, which is our implementation language, or in Windows, which is a supported platform. Furthermore, since the files are a SHARED resource it is not appropriate for them to be hardlinked into the sandbox. If the application uses "../foo.txt" they are aware that they are leaving the sandbox and that they need to play nicely. > the task execution environment should have a current working directory that > is task specific > -------------------------------------------------------------------------------------------- > > Key: HADOOP-673 > URL: http://issues.apache.org/jira/browse/HADOOP-673 > Project: Hadoop > Issue Type: Bug > Components: mapred > Affects Versions: 0.7.2 > Reporter: Owen O'Malley > Assigned To: Mahadev konar > Fix For: 0.9.0 > > > The tasks should be run in a work directory that is specific to a single > task. In particular, I'd suggest using the <local>/jobcache/<jobid>/<taskid> > as the current working directory. -- 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
