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

TezQA commented on TEZ-3465:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12832821/TEZ-3465.2.patch
  against master revision c9b09cb.

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 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 3.0.1) 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/2033//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2033//console

This message is automatically generated.

> Support broadcast edge into cartesian product vertex and forbid other edges
> ---------------------------------------------------------------------------
>
>                 Key: TEZ-3465
>                 URL: https://issues.apache.org/jira/browse/TEZ-3465
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Zhiyuan Yang
>            Assignee: Zhiyuan Yang
>         Attachments: TEZ-3465.1.patch, TEZ-3465.2.patch
>
>
> Cartesian product vertex manager should support other incoming edge type. 
> Currently only broadcast edge is necessary, although potentially more edge 
> types could also be. Custom edge need its own vertex manager which can't work 
> with Cartesian product VM, so it has to be forbade.



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

Reply via email to