Rong Rong

@siddharthteotia @jackjlli any concerns? Probably won't make it to 0.11 since release branch has been cut but we should merge this to master I think

@siddharthteotia @Jackie-Jiang @yupeng9 ^

+1. @atris

let's wait for #9176

fetch unorder is supported but we should still limit the number of rows returned at final stage.

do we want to support any boolean functions like * [ ] MATCH_ANY * [ ] MATCH_ALL * [ ] MATCH_NONE (all of these are element-wise predicate evaluators)

is there a backward compatibility story for this change. - if the header is broken but somehow the payload is ok. what's the behavior before/after this change - if header...

see: https://calcite.apache.org/docs/reference.html#ddl-extensions - `DESCRIBE TABLE ` should be parsable by calcite - `SHOW TALBES` might not be, - although we can make it as an alias of `DESCRIBE DATABASE "default"`...

> I think I finally found why the test was failing. It was due to a `cmp >= 0` assertion that should be `cmp > Things to know about: >...

please share your minimal reproducible query and table configuration. I suspect this would be related to converting a literal value to timestamp using scalar function at compile time