[
https://issues.apache.org/jira/browse/HADOOP-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635325#action_12635325
]
Steve Loughran commented on HADOOP-4285:
----------------------------------------
I dont think you could put the task current working directy in there unless it
was changed for every single node the task got run on, and not made
pre-configurable. If you make it a config variable that people submitting jobs
can set, it would just be a new way to raise support calls.
> A way to get tasks current working directory via JobConf
> --------------------------------------------------------
>
> Key: HADOOP-4285
> URL: https://issues.apache.org/jira/browse/HADOOP-4285
> Project: Hadoop Core
> Issue Type: Wish
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Lohit Vijayarenu
> Priority: Minor
>
> It would be good to have tasks know its current working directory via
> JobConf, instead of deriving the same or trying to get local current working
> directory. I see that we already derive that while updating classpath. Would
> it be good idea to have it as a config variable to make it available in task
> execution environment?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
