You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge?
It appears that there is no good way to know if the bloom filter code is working via logging or metrics 🤔
We have metrics on ParquetExec that explain when row groups are pruned, but now that we can prune them via statistics or bloom filters, we can't tell which was used in a particular query
Among other things this meant it was hard to reproduce / diagnose issues like #8685
Is your feature request related to a problem or challenge?
It appears that there is no good way to know if the bloom filter code is working via logging or metrics 🤔
We have metrics on ParquetExec that explain when row groups are pruned, but now that we can prune them via statistics or bloom filters, we can't tell which was used in a particular query
Among other things this meant it was hard to reproduce / diagnose issues like #8685
Describe the solution you'd like
Add some metrics for parquet pruning
Describe alternatives you've considered
@my-vegetable-has-exploded has a branch that could be a good starting point:
I check it by the metric I add myself(like https://github.com/apache/arrow-datafusion/compare/main...my-vegetable-has-exploded:arrow-datafusion:metric-sbbf?expand=1) , Should
Additional context
No response
The text was updated successfully, but these errors were encountered: