You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Rui Wang (Jira)" <ji...@apache.org> on 2019/10/02 18:42:00 UTC

[jira] [Commented] (BEAM-7049) Merge multiple input to one BeamUnionRel

    [ https://issues.apache.org/jira/browse/BEAM-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943072#comment-16943072 ] 

Rui Wang commented on BEAM-7049:
--------------------------------

Sorry [~sridharG] I probably have missed your message and indeed we are waiting each other.  Ok you actually some help on how to split UNION ALL and UNION right? Give me sometime to investigate and see what I can get. I will very likely to check how FlinkSQL does such optimization as they also use Calcite but has been much mature over us.

> Merge multiple input to one BeamUnionRel
> ----------------------------------------
>
>                 Key: BEAM-7049
>                 URL: https://issues.apache.org/jira/browse/BEAM-7049
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Rui Wang
>            Assignee: sridhar Reddy
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> BeamUnionRel assumes inputs are two and rejects more. So `a UNION b UNION c` will have to be created as UNION(a, UNION(b, c)) and have two shuffles. If BeamUnionRel can handle multiple shuffles, we will have only one shuffle



--
This message was sent by Atlassian Jira
(v8.3.4#803005)