Uh oh!
There was an error while loading. Please reload this page.
[SPARK-36647][SQL][TESTS] Push down Aggregate (Min/Max/Count) for Parquet if filter is on partition col - #34248
[SPARK-36647][SQL][TESTS] Push down Aggregate (Min/Max/Count) for Parquet if filter is on partition col#34248huaxingao wants to merge 5 commits into
Conversation
… filter is on partition col
SparkQA
commented
Oct 12, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 12, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 12, 2021
Test build #144110 has finished for PR 34248 at commit
|
| val enableVectorizedReader = Seq("false", "true") | ||
| for (testVectorizedReader <- enableVectorizedReader) { |
There was a problem hiding this comment.
nit: we can be more scala here, but not a big deal:
Seq("false", "true").foreach { enableVectorizedReader =>
withSQLConf(...) {
...
}
}
huaxingao
commented
Oct 13, 2021
cc @viirya Could you please take a look when you have time? Thanks! |
| Seq("false", "true").foreach { enableVectorizedReader => | ||
| withSQLConf(SQLConf.PARQUET_AGGREGATE_PUSHDOWN_ENABLED.key -> "true", | ||
| vectorizedReaderEnabledKey -> enableVectorizedReader) { | ||
| val max = sql("SELECT max(id) FROM tmp WHERE p = 0") |
There was a problem hiding this comment.
Can you add other two supported aggregate functions? And how about group by on partition column case?
There was a problem hiding this comment.
added.
Group by on partition column is a little more complicated and needs some code changes: currently, we only have the aggregate values in the returned row. For group by on partition column, we will need to pass down the partition col value and prepend that value to the aggregation row. I will have a separate PR for that work.
SparkQA
commented
Oct 13, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 13, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 13, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 13, 2021
Kubernetes integration test starting |
| // However, if the filter or group by is on partition column, | ||
| // max/min/count can still be pushed down |
There was a problem hiding this comment.
So group by on partition column is not supported yet. Then this comment is not correct.
SparkQA
commented
Oct 13, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 13, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 13, 2021
Test build #144177 has finished for PR 34248 at commit
|
SparkQA
commented
Oct 13, 2021
Test build #144180 has finished for PR 34248 at commit
|
SparkQA
commented
Oct 18, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 18, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 19, 2021
Test build #144380 has finished for PR 34248 at commit
|
viirya
commented
Oct 26, 2021
retest this please |
viirya
commented
Oct 26, 2021
I'll merge this after CI, since last CI was a few days ago. |
SparkQA
commented
Oct 26, 2021
Test build #144626 has started for PR 34248 at commit |
SparkQA
commented
Oct 26, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 26, 2021
Kubernetes integration test status failure |
viirya
commented
Oct 27, 2021
retest this please |
SparkQA
commented
Oct 27, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 27, 2021
Test build #144633 has finished for PR 34248 at commit
|
huaxingao
commented
Oct 27, 2021
retest this please |
SparkQA
commented
Oct 27, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 27, 2021
Kubernetes integration test starting |
SparkQA
commented
Oct 27, 2021
Kubernetes integration test status failure |
SparkQA
commented
Oct 27, 2021
Test build #144636 has finished for PR 34248 at commit
|
viirya
commented
Oct 27, 2021
Thanks! Merging to master. |
What changes were proposed in this pull request?
I just realized that with the changes in #33650, the restriction for not pushing down Min/Max/Count for partition filter was already removed. This PR just added test to make sure Min/Max/Count in parquet are pushed down if filter is on partition col.
Why are the changes needed?
To complete the work for Aggregate (Min/Max/Count) push down for Parquet
Does this PR introduce any user-facing change?
No
How was this patch tested?
new test