[
https://issues.apache.org/jira/browse/TEZ-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002167#comment-14002167
]
Hitesh Shah commented on TEZ-1027:
----------------------------------
Comments:
- The change to use the property looks fine. However, when actually using
this dir, the job should be using an appId specific sub-dir within the staging
dir. The same code executes for multiple application instances hence something
like the appId probably needs to be used to prevent any clashes. This only
holds for any data dir being created by the user code ( i.e. not tez framework
code ). In this scenario, OrderedWordCount is user code.
> orderedwordcount needs to respect tez.staging-dir property
> ----------------------------------------------------------
>
> Key: TEZ-1027
> URL: https://issues.apache.org/jira/browse/TEZ-1027
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Yesha Vora
> Priority: Trivial
> Labels: patch
> Attachments: TEZ-1027.1.patch
>
>
> Currently orderedwordcount job is not respecting tez.staging-dir property.
> When AM recovery is enabled, the job recover data is being stored at
> /user/<username>/.staging/<app id> location instead the path defined by
> tez.staging-dir .
--
This message was sent by Atlassian JIRA
(v6.2#6252)
