[ 
https://issues.apache.org/jira/browse/TEZ-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338237#comment-14338237
 ] 

Hadoop QA commented on TEZ-391:
-------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12701014/TEZ-391-WIP-4.patch
  against master revision 1ccb0be.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 10 new 
or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 181 javac 
compiler warnings (more than the master's current 180 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/231//testReport/
Javac warnings: 
https://builds.apache.org/job/PreCommit-TEZ-Build/231//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/231//console

This message is automatically generated.

> SharedEdge - Support for passing same output from a vertex as input to two 
> different vertices
> ---------------------------------------------------------------------------------------------
>
>                 Key: TEZ-391
>                 URL: https://issues.apache.org/jira/browse/TEZ-391
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Rohini Palaniswamy
>            Assignee: Jeff Zhang
>         Attachments: Shared Edge Design.pdf, TEZ-391-WIP-1.patch, 
> TEZ-391-WIP-2.patch, TEZ-391-WIP-3.patch, TEZ-391-WIP-4.patch
>
>
>   We need this for lot of usecases. For cases where multi-query is turned off 
> and for optimizing unions. Currently those are BROADCAST or ONE-ONE edges and 
> we write the output multiple times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to