Re:Re: Re: Flink SQL: non-deterministic join behavior, is it expected?

2023-10-24 Thread Xuyang
Hi, the plan seems correct. You can debug in StreamingJoinOperator#processLeft and #processRight by writing an IT case to see what happened. Do these records arrive the join operator out of order? If they are, maybe you can check the order while these data are sent in source. --

Re: Re: Flink SQL: non-deterministic join behavior, is it expected?

2023-10-23 Thread Yaroslav Tkachenko
Hi, sure, sharing it again: SELECT a.funder, a.amounts_added, r.amounts_removed FROM table_a AS a JOIN table_b AS r ON a.funder = r.funder and the Optimized Execution Plan: Calc(select=[funder, vid AS a_vid, vid0 AS r_vid, amounts_added, amounts_removed]) +- Join(joinType=[InnerJoin],

Re: Flink SQL: non-deterministic join behavior, is it expected?

2023-10-20 Thread Yaroslav Tkachenko
Hi Xuyang, A shuffle by join key is what I'd expect, but I don't see it. The issue only happens with parallelism > 1. > do you mean the one +I record and two +U records arrive the sink with random order? Yes. On Fri, Oct 20, 2023 at 4:48 AM Xuyang wrote: > Hi. Actually the results that