debugmiller opened a new issue, #1428: URL: https://github.com/apache/iceberg-rust/issues/1428
### Is your feature request related to a problem or challenge? Running `SELECT COUNT(1)` when using iceberg-datafusion results in a table scan. This can be avoided by implementing [ExecutionPlan::statistics](https://docs.rs/datafusion/latest/datafusion/physical_plan/trait.ExecutionPlan.html#method.statistics). Datafusion does this for its built-in parquet scanner by fetching the statistics from parquet metadata when [constructing the ExecutionPlan](https://github.com/apache/datafusion/blob/367331e4a83412f450fa4b7b41aad6dc3624d04b/datafusion/core/src/datasource/listing/table.rs#L914). I was looking to implement this in a similar way (at least for tables without deletes) by iterating over the `ManifestEntry`s and summing the `record_count`s. I have a draft PR but wanted to confirm this approach is acceptable before putting in the work to clean it up. ### Describe the solution you'd like `count(*)` in datafusion does not perform a table scan ### Willingness to contribute I would be willing to contribute to this feature with guidance from the Iceberg Rust community -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
