Open King-Dylan opened 2 years ago
After discussion with @winoros We thought the main problem here is where to decorrelate an apply as join. By now TiDB always dives down to find the correlated inner operator, making the apply
to be a join
beneath it. which will cause the join to execute as early as possible, as close to the data source as possible. For this case, the correlated selection operator in the inner side can do the reverse way, pulling up as close to apply as possible.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
3. What did you see instead (Required)
10 rows in set (0.00 sec)
4. What is your TiDB version? (Required)
v6.0.0