Related: #11, #68, #127 Ran with no datafusion optimizations (all of our own optimizations) Tests were done for whether or not the query works with perfbench. Query result may be incorrect, but it compiles and runs - [x] Q1 - Broken in same way as [previously found issue](https://github.com/cmu-db/optd/issues/) - perftest issue? - [ ] Q2 - Plan generated is so bad that it causes an overflow in datafusion's cardinality estimation - [x] Q3 - [ ] Q4 - Depends on subquery unnesting EXISTS support - [x] Q5 - [x] Q6 - [x] Q7 - [x] Q8 - [x] Q9 - [x] Q10 - [x] Q11 - Bug: `test panicked: Column index 2 out of bounds 2 + 0` - [x] Q12 - [x] Q13 - [x] Q14 - [x] Q15 - [ ] Q16 - Depends on subquery unnesting IN support - May depend also on left anti join - [x] Q17 - Bug: `test panicked: assertion failed: i + left_schema_size < left_schema_size + right_schema_size` - [ ] Q18 - Depends on subquery unnesting IN support - May depend also on left semi join - [x] Q19 - [ ] Q20 - Depends on subquery unnesting IN support - May depend also on left semi join - [ ] Q21 - Depends on subquery unnesting EXISTS support - May depend also on left semi and left anti join - [ ] Q22 - Depends on subquery unnesting IN and EXISTS support - May depend also on left anti join
Related: #11, #68, #127
Ran with no datafusion optimizations (all of our own optimizations)
Tests were done for whether or not the query works with perfbench. Query result may be incorrect, but it compiles and runs
test panicked: Column index 2 out of bounds 2 + 0test panicked: assertion failed: i + left_schema_size < left_schema_size + right_schema_size