[
https://issues.apache.org/jira/browse/TEZ-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671986#comment-15671986
]
Bikas Saha commented on TEZ-1190:
---------------------------------
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.
I have not looked at the code for a while :) With that caveat, 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. You are right that since some user code
also runs in egde/vm plugins the plugin wrapper layer also needs to have the
default case handling. That would be similar to the handling on the client side.
Either ways work. I guess the reason I am persisting on this is that I think
the separation of concerns would be better in the case where this is handled in
the API layer. After all this is more of an API thing (which until now has
leaked into the server side).
> 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)
