[
https://issues.apache.org/jira/browse/KUDU-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186406#comment-16186406
]
Will Berkeley commented on KUDU-2162:
-------------------------------------
[~twmarshall] This info is needed at a per-scanner level, correct? Kudu doesn't
presently have any scanner-level metrics, only server- and tablet-scoped
metrics.
Clearly there's a good use case for scanner metrics here, so maybe we should
figure out a good way to do it.
> Expose stats about scan filters
> -------------------------------
>
> Key: KUDU-2162
> URL: https://issues.apache.org/jira/browse/KUDU-2162
> Project: Kudu
> Issue Type: Improvement
> Components: client
> Reporter: Thomas Tauber-Marshall
>
> Impala is working on implementing runtime filters that get pushed down into
> Kudu using KuduScanner::AddConjunctPredicate()
> It would be useful for perf analysis and debugging to be able to include info
> in Impala's runtime profile about the effectiveness of the filters, eg.
> number of rows that are filtered.
> This would probably require at least two counters:
> - # of blocks that are entirely skipped
> - # of rows that are filtered from blocks that aren't entirely skipped
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
