[
https://issues.apache.org/jira/browse/BEAM-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122917#comment-17122917
]
Beam JIRA Bot commented on BEAM-6719:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Allow multiple Joins in the same pipeline
> -----------------------------------------
>
> Key: BEAM-6719
> URL: https://issues.apache.org/jira/browse/BEAM-6719
> Project: Beam
> Issue Type: Improvement
> Components: extensions-java-join-library
> Reporter: Daniel Mescheder
> Priority: P2
> Labels: stale-P2
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently it is not possible to have multiple joins in the same pipeline
> without wrapping them in individual PTransforms as this would generate name
> clashes.
> Consider the following test case:
> {code:java}
> @Test
> public void testMultipleJoinsInSamePipeline() {
> leftListOfKv.add(KV.of("Key2", 4L));
> PCollection<KV<String, Long>> leftCollection = p.apply("CreateLeft",
> Create.of(leftListOfKv));
> rightListOfKv.add(KV.of("Key2", "bar"));
> PCollection<KV<String, String>> rightCollection = p.apply("CreateRight",
> Create.of(rightListOfKv));
> expectedResult.add(KV.of("Key2", KV.of(4L, "bar")));
> PCollection<KV<String, KV<Long, String>>> output1 =
> Join.innerJoin(leftCollection, rightCollection);
> PCollection<KV<String, KV<Long, String>>> output2 =
> Join.innerJoin(leftCollection, rightCollection);
> PAssert.that(output1).containsInAnyOrder(expectedResult);
> PAssert.that(output2).containsInAnyOrder(expectedResult);
> p.run();
> }
> {code}
> This fails because of clashing names in the pipeline and there is currently
> no way to use the join library to give the joins different names.
> Therefore I find myself routinely wrapping joins in new PTransforms which
> leads me to believe that this should be part of the library itself.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
