andygrove commented on code in PR #9988:
URL: https://github.com/apache/arrow-datafusion/pull/9988#discussion_r1558419795
##########
datafusion/core/src/datasource/provider.rs:
##########
@@ -161,20 +161,73 @@ pub trait TableProvider: Sync + Send {
/// Specify if DataFusion should provide filter expressions to the
/// TableProvider to apply *during* the scan.
///
+ /// Some TableProviders can evaluate filters more efficiently than the
+ /// `Filter` operator in DataFusion, for example by using an index.
+ ///
/// The return value must have one element for each filter expression
passed
/// in. The value of each element indicates if the TableProvider can apply
- /// that particular filter during the scan.
+ /// that particular filter during the scan. The position in the return
value
+ /// Vec corresponds to the expression in the `filters` input.
+ ///
+ /// Here is an example of how this can be done:
+ ///
+ /// ```rust
+ /// use datafusion::error::{Result, DataFusionError};
+ /// use datafusion_expr::{Expr, TableProviderFilterPushDown};
+ ///
+ /// // Override the supports_filters_pushdown to evaluate which
expressions
+ /// // to accept as pushdown predicates.
+ /// fn supports_filters_pushdown(&self, filters: &[&Expr]) ->
Result<Vec<TableProviderFilterPushDown>> {
Review Comment:
This doesn't compile for me when I run `cargo test --doc` locally and is
also failing in CI. One issue here is that this function needs to be part of an
`impl` block for a struct rather than a standalone function, otherwise there is
no `self` to refer to. I also added some comments for smaller issues that
caused compilation issues locally.
--
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]
