optd
optd copied to clipboard
Tracking: make sure optd does not crash for TPC-H queries
- [x] Q1 #78
- 🚧 Not working in perftest:
Error: ArrowError(NotYetImplemented("Unsupported Interval Expression with value \"115 day (3) seconds\""))
- 🚧 Not working in perftest:
- [x] Q2 #80
- [x] Q3 #86
- [ ] Q4
- optd panics with
cannot find best binding for group
(Not supporting left semi join)
- optd panics with
- [x] Q5 #69
- [x] Q6 #69
- 🚧 Working in optd but not in DataFusion:
Error: Arrow error: Invalid argument error: Invalid comparison operation: Decimal128(15, 2) >= Decimal128(20, 0)
- 🚧 Working in optd but not in DataFusion:
- [x] Q7 #72
- [x] Q8 https://github.com/cmu-db/optd/pull/64
- [x] Q9 #72
- [x] Q10 #78
- [x] Q11
- Non-equal join filer
- [x] Q12 #77
- [x] Q13
- DF
Join
filter
saysFilters applied during join (non-equi conditions)
, but there can actually be equal comparisons! - Non-equal join filter
- DF
- [x] Q14 #78
- [x] Q15 #86
- 🚧 Not working in perftest:
unsupported plan node: CreateView: Bare { table: "revenue0" }
- 🚧 Not working in perftest:
- [ ] Q16
- optd panics with
cannot find best binding for group
(Not supporting left anti join)
- optd panics with
- [x] Q17 #86
- [ ] Q18
- optd panics with
cannot find best binding for group
(Not supporting left semi join)
- optd panics with
- [x] Q19 #77
- [ ] Q20
- optd panics with
cannot find best binding for group
(Not supporting left semi join)
- optd panics with
- [ ] Q21
- optd panics with
cannot find best binding for group
(Not supporting left semi and left anti join)
- optd panics with
- [ ] Q22
- optd panics with
cannot find best binding for group
(Not supporting left anti join)
- optd panics with
Missing features
- [x] Subquery: Q2, Q3, Q4, Q11, Q16, Q17, Q20, Q21, Q22
- Correlated subquery is not supported in DF physical optimizer. DF's logical optimizer eliminates
OuterReferenceColumn
by moving the column to the outer query. Since we do not know how to access columns of the outer query, I think we should enable DF's logical optimizer when dealing with subqueries. - ~With DF's logical optimizer enabled, we get
Error during planning: table 'datafusion.public.xxxx' not found
error.~ When usingexplain_with_logical
in the planner test, make sure to execute the DDLs withexecute_with_logical
!
- Correlated subquery is not supported in DF physical optimizer. DF's logical optimizer eliminates
- [x]
InListExpr
: Q12, Q16, Q19 #77 - [x]
IntervalMonthDayNano
: Q1, Q10, Q14(#78) - [x] Multiple (non-equal) predicates for one join: Q11, Q13, Q22
- [x]
ColumnRefPropertyBulder
- [x]
LogOp
: Q16
- [x]
- [ ] Left anti and left semi join: Q4, Q16, Q18, Q20, Q21, Q22