Commit d5d7e48
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes apache#123` indicates that this PR will close issue apache#123.
-->
Follow up to apache#19977
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->
There are two similar parquet page pruning metrics:
1. page_index_pages_pruned -- how many pages are pruned/kept
2. page_index_rows_pruned -- The same as 1, but displayed in number of
rows, instead of the page count
Displaying both of them in the `summary` `EXPLAIN ANALYZE` level I think
can be too verbose, so the row metrics is changed to only display in the
verbose level.
Demo:
```sh
> set datafusion.explain.analyze_level='summary';
0 row(s) fetched.
Elapsed 0.039 seconds.
> explain analyze
select * from '/Users/yongting/data/tpch_sf1/lineitem.parquet'
where l_orderkey < 2000000;
> ...
DataSourceExec: ...metrics=[...page_index_pages_pruned=102 total → 98 matched...]
> set datafusion.explain.analyze_level='dev';
0 row(s) fetched.
Elapsed 0.039 seconds.
> explain analyze
select * from '/Users/yongting/data/tpch_sf1/lineitem.parquet'
where l_orderkey < 2000000;
> ...
DataSourceExec: ...metrics=[...page_index_pages_pruned=102 total → 98 matched, page_index_rows_pruned=2.08 M total → 2.00 M matched,...]
```
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
4. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
1 parent 7000998 commit d5d7e48
3 files changed
Lines changed: 7 additions & 8 deletions
File tree
- datafusion
- datasource-parquet/src
- sqllogictest/test_files
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
118 | 118 | | |
119 | 119 | | |
120 | 120 | | |
121 | | - | |
122 | | - | |
123 | | - | |
124 | | - | |
125 | | - | |
126 | 121 | | |
127 | 122 | | |
128 | 123 | | |
| |||
179 | 174 | | |
180 | 175 | | |
181 | 176 | | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
182 | 181 | | |
183 | 182 | | |
184 | 183 | | |
| |||
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
104 | 104 | | |
105 | 105 | | |
106 | 106 | | |
107 | | - | |
| 107 | + | |
108 | 108 | | |
109 | 109 | | |
110 | 110 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
63 | 63 | | |
64 | 64 | | |
65 | 65 | | |
66 | | - | |
| 66 | + | |
67 | 67 | | |
68 | 68 | | |
69 | 69 | | |
| |||
72 | 72 | | |
73 | 73 | | |
74 | 74 | | |
75 | | - | |
| 75 | + | |
76 | 76 | | |
77 | 77 | | |
78 | 78 | | |
| |||
0 commit comments