alamb commented on PR #5362:
URL:
https://github.com/apache/arrow-datafusion/pull/5362#issuecomment-1440963131
> Though I agree that would make the plans read better, I think the index
needs to live within the TableProvider / TableScan node because we don't want
to return all of the filtered data any farther up the tree than we need to,
much like predicate pushdown.
One way might be to extend the `TableScan` display to include something from
the `TablerProvider`
So something like this perhaps
```rust
trait TableProvider {
/// return optional extra content to include in an EXPLAIN plan
fn explain_plan_extras(&self) -> Option<String>;
}
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
