Nicholas Gates

Call check_signals in the scan to support signal handlers

1

https://docs.rs/pyo3/latest/pyo3/marker/struct.Python.html#method.check_signals Ideally, we call this at various points in our Rust code, I think a nice place would be for in the "next" of a record batch reader? This will...

https://github.com/ClickHouse/ClickBench/

Currently pruning says whether a chunk is _all false_ and can be thrown away. But we don't do the inverse and use stats to say that a chunk is _all...

And DateTimeParts should propgate sortedness stats during encode

Much more ergonomic at the expense of a few bytes. e.g. `us|UTC`

Most "table provider" interfaces, including DataFusion, Arrow Dataset, Polars, etc all support pushing down limits.

We have a half-implemented combine_stats function that does the right thing, but Statistics::inherit does not

Short-circuit to find the result nullability of an expression