[
https://issues.apache.org/jira/browse/TEZ-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672232#comment-15672232
]
Zhiyuan Yang commented on TEZ-1190:
-----------------------------------
{quote}
Still don't understand why making named/unnamed exclusive is going to help. An
example would help. Having the backed completely named would render the new
feature enabled/disabled/exclusive/hydrid become an purely client side API
thing. Which is naturally seems to be.
{quote}
Your understand is corret. It is purely client side API thing. We don't support
hybrid case just it's not worth the effort in the first step. Using hybrid case
could be painful to use because users have to make sure all kinds of name
collision between user-given name and default name, and it'd better just use
named edge everywhere.
{quote}
its not clear to me why having the AM handle default names makes things easier
vs doing it at the client and making the AM agnostic.
{quote}
I wanted to say 'whoever assign the default doesn't really matter because it's
easy to do in either client or AM', but I just found one scenario where AM/task
must know whether edge is named by user or by default. In task side, we need to
provide a output map to processor. The keys of map are destination edge names
in named case, but should be destination vertex names (which is different from
destination edge names) in unnamed case to keep compatibility. Tasks have not
way to decide which name to use as key unless they know whether edge is named
by user or not. This is not a issue for input map because default edge names
are same with source vertex names.
> Allow multiple edges between two vertices
> -----------------------------------------
>
> Key: TEZ-1190
> URL: https://issues.apache.org/jira/browse/TEZ-1190
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Daniel Dai
> Assignee: Zhiyuan Yang
> Attachments: NamedEdgeDesign.pdf, TEZ-1190.prototype.patch
>
>
> This will be helpful in some scenario. In particular example, we can merge
> two small pipelines together in one pair of vertex. Note it is possible the
> edge type between the two vertexes are different.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
