Thank you Bikas for the quick reply! I will work around this for now

Kostas

On Wed, Oct 1, 2014 at 10:33 PM, Bikas Saha <[email protected]> wrote:

> Multiple edges between 2 vertices are not supported right now. The only
> use case that we could think of for that was the self-join case (which you
> also mention below). That is why we punted on it for the future. TEZ-1190
> <https://issues.apache.org/jira/browse/TEZ-1190> tracks the feature.
>
>
>
> Bikas
>
>
>
> *From:* Kostas Tzoumas [mailto:[email protected]]
> *Sent:* Wednesday, October 01, 2014 11:45 AM
> *To:* [email protected]
> *Subject:* Self-join-style DAGs
>
>
>
> Hi,
>
>
>
> I am generating a DAG in which a vertex has two input edges that originate
> on the same vertex (imagine a self-join, or here is an ASCII drawing for
> you :-).
>
>
>
>     -------------------
>
>     |                     |
>
>     |                    V
>
>
>
> Source ---> Operator
>
>
>
> As far as I understand, every vertex in Tez needs to have a unique name in
> the DAG, and logical inputs are offered at runtime as a map of vertex names
> to inputs. Therefore, my operator above has only one logical input.
>
>
>
> Is that intentional? If the operator logic is designed with two logical
> inputs in mind (e.g., a join), what is the best way to model this? Create
> many readers per input, duplicate the source vertex, ...?
>
>
>
> Perhaps someone has run into a similar situation.
>
>
>
> Thanks,
>
> Kostas
>
>
>
>
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

Reply via email to