[
https://issues.apache.org/jira/browse/SQOOP-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110550#comment-14110550
]
Jarek Jarcec Cecho commented on SQOOP-1392:
-------------------------------------------
Based on reading the MapReduce APIs it seems that the best way might be to load
Java property {{java.io.tmpdir}}. MapReduce have configuration option
[mapreduce.task.tmp.dir|https://hadoop.apache.org/docs/r2.4.0/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml]
through which user can configure where the task temporary directory should be
located. This configuration option seems to be resolved either to the task
working directory or any absolute path given by the user and passed to the
Mapper/Reducer via {{java.io.tmpdir}}:
{quote}
To set the value of tmp directory for map and reduce tasks. If the value is an
absolute path, it is directly assigned. Otherwise, it is prepended with task's
working directory. The java tasks are executed with option
-Djava.io.tmpdir='the absolute path of the tmp dir'. Pipes and streaming are
set with environment variable, TMPDIR='the absolute path of the tmp dir'
{quote}
> Create the temporary directory inside task working dir rather then in tmp
> -------------------------------------------------------------------------
>
> Key: SQOOP-1392
> URL: https://issues.apache.org/jira/browse/SQOOP-1392
> Project: Sqoop
> Issue Type: Improvement
> Components: tools
> Reporter: Qian Xu
> Priority: Minor
> Attachments: patch.diff
>
>
> Several mappers will create a temporary directory in /tmp ranther then inside
> the task working directory. We should change the pattern.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
