xuyangzhong opened a new pull request, #2000: URL: https://github.com/apache/fluss/pull/2000
### Purpose Linked issue: close #1986 <!-- What is the purpose of the change --> ### Brief change log Clarify the supported Flink versions for delta join. ### Tests I have manually verified it with: - Latest Flink 2.1 (can be regarded as 2.1.2) with Fluss 0.8 - Latest Flink 2.2 (can be regarded as 2.2.0) with Fluss 0.8 Steps: 1. build the flink with these latest specific branches manually (because currently they are not released), and move fluss connector `fluss-flink-2.1-0.8.0-incubating.jar` and nexmark connector (we use nexmark connector to mock data, so we need to build https://github.com/nexmark/nexmark and get the nexmark connector jar `nexmark-flink-0.3-SNAPSHOT.jar` in `nexmark-flink/target/`) to `FLINK_HOME/lib` 2. start flink standalone cluster with new configuration `numberOfTaskSlots` 4 , and start fluss local cluster 3. use flink sql client to run `./bin/sql-client.sh -f prepare_table.sql` to prepare three tables used for two sources and one sink. 3.1. for Flink 2.1.2, the DDLs are [prepare_table_2.1.sql](https://github.com/user-attachments/files/23627610/prepare_table_2.1.sql) 3.2. for Flink 2.2.0, the DDLs are [prepare_table_2.2.sql](https://github.com/user-attachments/files/23627625/prepare_table_2.2.sql) 4. run the delta join job by sql client `./bin/sql-client.sh -f run_delta_join.sql` [run_delta_join.sql](https://github.com/user-attachments/files/23627635/run_delta_join.sql) 5. insert data to source tables by sql client `./bin/sql-client.sh -f insert_data.sql` [insert_data.sql](https://github.com/user-attachments/files/23627660/insert_data.sql) Now you can see the delta join job is running successfully and is processing data. <img width="4584" height="2118" alt="image" src="https://github.com/user-attachments/assets/c7911966-bf42-41e4-ad89-9740fe52408d" /> ### API and Format None. ### Documentation None. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
