[
https://issues.apache.org/jira/browse/TEZ-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305808#comment-14305808
]
Rohini Palaniswamy commented on TEZ-391:
----------------------------------------
bq. I still think ShareOutputEdge is more suitable. Because for GroupInputEdge,
there's multiple inputs from upstream vertices, we group them together into
GroupInput. While for ShareOutputEdge, there's actually only one output from
upstream vertex. So from semantic perspective I think ShareOutputEdge is better.
Sounds good. But can we call it SharedOutputEdge instead of ShareOutputEdge?
bq. Besides, I am thinking is it necessary to expose the
GroupInputEdge/ShareOutputEdge as public API. IMO, I don't think it is
necessary.
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.
> 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)
