You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2015/05/22 02:08:18 UTC

[jira] [Comment Edited] (TEZ-2409) Allow different edges to have different routing plugins

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

Bikas Saha edited comment on TEZ-2409 at 5/22/15 12:07 AM:
-----------------------------------------------------------

The TestVertexImpl time out does not repro locally. [~hitesh] [~sseth] [~rajesh.balamohan] [~zjffdu] Please review. The patch enabled legacy and current routing to co-exist on a given vertex. This will allow older Hive plugins to work with new Tez versions and we will not lose out on memory optimizations on the other edges. Tests added for the changes.


was (Author: bikassaha):
The TestVertexImpl time out does not repro locally. [~hitesh] [~sseth] [~rajesh.balamohan] Please review. The patch enabled legacy and current routing to co-exist on a given vertex. This will allow older Hive plugins to work with new Tez versions and we will not lose out on memory optimizations on the other edges.

> 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)