[
https://issues.apache.org/jira/browse/BEAM-7049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913442#comment-16913442
]
sridhar Reddy commented on BEAM-7049:
-------------------------------------
Thanks for the quick update. I agree that it is helpful to have general n
implementation and I was thinking along the same lines as you are.
I had trouble with the following part when I went that route but I didn't spend
too much time debugging it. The .and(current i) doesn't work as expected. I may
have to use some casting but let me work on it before coming back with
questions.
------
KeyedPCollectionTuple.of(), and then for (i -> 1, n)
KeyedPCollectionTuple.and(current i);}
---------
I just wanted to make sure I am on the right track before I make too many
changes.
> 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: 20m
> 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.2#803003)
