[
https://issues.apache.org/jira/browse/TEZ-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514913#comment-14514913
]
TezQA commented on TEZ-2368:
----------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728479/TEZ-2368.2.txt
against master revision 21d4e2d.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/548//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/548//console
This message is automatically generated.
> Make the dag number available in Context classes
> ------------------------------------------------
>
> Key: TEZ-2368
> URL: https://issues.apache.org/jira/browse/TEZ-2368
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-2368.1.txt, TEZ-2368.2.txt
>
>
> Provide the dag number, which is a unique number, for each dag running within
> an application in the TezInputContext, TezOutputContext, TezProcessorContext.
> When containers are re-used, or for external services, this can be used to
> generate intermediate data to a dag specific directory instead of an
> application specific directory, where it becomes difficult to differentiate
> between different dags.
> The DAG name does provide this - but is not suitable for use in a directory
> name. Hashing the name is an option, but can lead to collisions.
> Generating data into a dag specific directory will eventually only be usable
> when we move away from the default MR handler, or enhance it to support an
> additional parameter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
