Thanks Yingjie for pinging me.
Hi vtygoss,
Leonard is right, maybe you are using the wrong statistics information.
This caused the optimizer to select the **BROADCAST JOIN**
incorrectly. Unfortunately, Flink needs to broadcast a huge amount of data,
even gigabytes. This is really the performance
Hi, vtygoss
Thanks for the detail report, a quick reply as I wrote the
org.apache.flink.table.tpcds.TpcdsTestProgram in community, I guess you missed
table statistics information.
The table statistics information used in the TPC-DS e2e tests is constant for
1GB verification data set, I wrote
