Split out from #1577 (item 2).
Unlike CatalogProvider / SchemaProvider, wiring a plain-Python TableProvider subclass through to the Rust TableProvider trait needs a new RustWrappedPyTableProvider, analogous to RustWrappedPySchemaProvider in catalog.rs. It has to cover scan() returning an ExecutionPlan, supports_filters_pushdown, and statistics.
This is execution-engine work, not a typing-only change, so it doesn't belong in a typing PR. Opening as its own issue so the design (partial pushdown support, how statistics get surfaced to the Python side) can be discussed before someone picks it up.
Split out from #1577 (item 2).
Unlike
CatalogProvider/SchemaProvider, wiring a plain-PythonTableProvidersubclass through to the RustTableProvidertrait needs a newRustWrappedPyTableProvider, analogous toRustWrappedPySchemaProviderincatalog.rs. It has to coverscan()returning anExecutionPlan,supports_filters_pushdown, and statistics.This is execution-engine work, not a typing-only change, so it doesn't belong in a typing PR. Opening as its own issue so the design (partial pushdown support, how statistics get surfaced to the Python side) can be discussed before someone picks it up.