[
https://issues.apache.org/jira/browse/TEZ-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528831#comment-14528831
]
Bikas Saha commented on TEZ-2221:
---------------------------------
Agree. But multiple edges is a corner case (self-join) and supporting it is a
pretty large change. If we can get away with a workaround, I'd be happy with
that. Again, not saying that this work around works. But [~rohini] says it
works. So we need to verify how. It may be that this jira is not involved. In
which case, there is nothing to do. So we are fine with the check for now, we
can relax it later if needed.
To be clear (v1, v2) and (v2, v3) is allowed, (v1, v2) and (v1, v2, v3) is
allowed, but not (v1, v2) and (v1, v2). Right?
> VertexGroup name should be unqiue
> ---------------------------------
>
> Key: TEZ-2221
> URL: https://issues.apache.org/jira/browse/TEZ-2221
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Fix For: 0.7.0, 0.5.4, 0.6.1
>
> Attachments: TEZ-2221-1.patch, TEZ-2221-2.patch, TEZ-2221-3.patch,
> TEZ-2221-4.patch
>
>
> VertexGroupCommitStartedEvent & VertexGroupCommitFinishedEvent use vertex
> group name to identify the vertex group commit, the same name of vertex group
> will conflict. While in the current equals & hashCode of VertexGroup, vertex
> group name and members name are used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
