Re: Streaming join performance

Привет Артем! Are your tables backed by Kafka? If - yes, what if you use upsert-kafka connector from Table API , does it help to reduce the number of records in each subsequent join operator? I wrote a blog-p

Re: Streaming join performance

Hi, David Regarding the N-way join, this feature aims to address the issue of state simplification, it is on the roadmap. Technically there are no limitations, but we'll need some time to find a sensible solution. Best, Ron David Anderson 于2023年8月9日周三 10:38写道： > This join optimization sounds p

Re: Streaming join performance

This join optimization sounds promising, but I'm wondering why Flink SQL isn't taking advantage of the N-Ary Stream Operator introduced in FLIP-92 [1][2] to implement a n-way join in a single operator. Is there something that makes this impossible/impractical? [1] https://cwiki.apache.org/confluen

RE: Streaming join performance

Hi, we are also paying attention to this issue and have completed the validation of the minibatch join optimization including the intermediate message folding you mentioned. We plan to officially release it in Flink 1.19. This optimization could significantly improves the performance of join op