[
https://issues.apache.org/jira/browse/TEZ-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306425#comment-14306425
]
Jeff Zhang commented on TEZ-391:
--------------------------------
bq. Sounds good. But can we call it SharedOutputEdge instead of ShareOutputEdge?
Sure.
bq. We already use GroupInputEdge in pig. Refer to TezDAGBuilder. Not sure how
you can set up the edge for Vertex Group without that as the mergedinput
descriptor needs to be set for it.
This may need some api changes. As my understanding, the input descriptor
depends on the edge property. So the following API should be sufficient for
creating any kind of edges. Anyway, since this would change the api, it is just
a proposal , won't do it this jira.
{code}
Edge.create(vertex/vertexgroup, vertex/vertexgroup, edge_property)
{code}
> 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
>
>
> 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)
