[jira] [Updated] (KUDU-2162) Expose stats about scan filters

["Will Berkeley (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Berkeley updated KUDU-2162:
--------------------------------
    Code Review: https://gerrit.cloudera.org/#/c/8375/

[~twmarshall] At [~tlipcon]'s suggestion I switched to using elapsed time in nanos and bytes read as the metrics, since that should also give a rough estimate of the work done by a given scan. I just posted the review (linked above) and added you.


> 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
>            Assignee: Will Berkeley
>
> 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)