[ https://issues.apache.org/jira/browse/TEZ-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551446#comment-14551446 ]
TezQA commented on TEZ-2409: ---------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12733976/TEZ-2409.1.patch against master revision 20ef028. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 6 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:red}-1 core tests{color}. The following test timeouts occurred in : org.apache.tez.dag.app.dag.impl.TestVertexImpl Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/703//testReport/ Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/703//console This message is automatically generated. > Allow different edges to have different routing plugins > ------------------------------------------------------- > > Key: TEZ-2409 > URL: https://issues.apache.org/jira/browse/TEZ-2409 > Project: Apache Tez > Issue Type: Task > Reporter: Bikas Saha > Assignee: Bikas Saha > Priority: Critical > Attachments: TEZ-2409.1.patch > > > It may be useful to allow different edge manager plugin types based on > different requirements. In order to support this, we would need to support > different plugins per edge for routing the events on that edge. A motivating > scenario is when a custom plugin from an older release of a downstream > project is using older API's while the latest release of that project has > moved on to newer API's. This would allow both old and new releases to work > with the latest Tez framework as optimally as possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)