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

dalongliu edited comment on FLINK-38052 at 7/16/25 1:55 AM:
------------------------------------------------------------

[~kartikeypant] Can you help complete it by the end of this week? Otherwise, it 
will affect the Flink 2.1 release. Very thanks.


was (Author: lsy):
[~kartikeypant] Can you help complete it this week?

> Release Testing: Verify FLIP-516: New Streaming Multi-Way Join Operator
> -----------------------------------------------------------------------
>
>                 Key: FLINK-38052
>                 URL: https://issues.apache.org/jira/browse/FLINK-38052
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>    Affects Versions: 2.1.0
>            Reporter: dalongliu
>            Assignee: Kartikey Pant
>            Priority: Blocker
>              Labels: release-testing
>             Fix For: 2.1.0
>
>
> This issue aims to verify FLIP-516.
> We now support a StreamingMultiJoinOperator that performs a join across N 
> tables without intermediate state. We've done some testing and observed 
> considerable performance and state improvements for multiple chained joins 
> when they record amplification.
>  
> Now we'd like to have some cross team testing to validate it. We want to 
> cover the following cases
>  * Test 1: Enable multi joins, confirm 2/3 way inner joins are supported and 
> produce correct results. Materialized results should be the same as binary 
> joins.
>  * Test 2: Enable multi joins, confirm 2/3 way left joins are supported and 
> produce correct results. Materialized results should be the same as binary 
> joins.
>  * Test 3: Enable 5, 10, 20, x-way joins with/without primary keys and 
> confirm output plans look good with `explain`.
>  * Test 4: Enable 5, 10, 20, x-way joins with/without primary keys and 
> confirm they run as expected - checking results' correctness here is usually 
> complicated and not strictly required.
>  
> Multi joins can be enabled with ??SET 'table.optimizer.multi-join.enabled' = 
> 'true';.?? Currently, we have streaming mode support for inner and left joins.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to