Uh oh!
There was an error while loading. Please reload this page.
[WIP][SPARK-32833][SQL] JDBC V2 Datasource aggregate push down - #32061
[WIP][SPARK-32833][SQL] JDBC V2 Datasource aggregate push down#32061baibaichen wants to merge 2 commits into
Conversation
baibaichen
commented
Apr 6, 2021
cc @huaxingao |
568d726 to
be4e673Comparebe4e673 to
75f8fdcComparewangyum
commented
Apr 7, 2021
ok to test. |
wangyum
commented
Apr 7, 2021
add to whitelist. |
SparkQA
commented
Apr 7, 2021
Kubernetes integration test starting |
SparkQA
commented
Apr 7, 2021
Kubernetes integration test status failure |
baibaichen
commented
Apr 7, 2021
ok to test. |
SparkQA
commented
Apr 7, 2021
Kubernetes integration test starting |
SparkQA
commented
Apr 7, 2021
Kubernetes integration test status failure |
SparkQA
commented
Apr 7, 2021
Test build #136977 has finished for PR 32061 at commit
|
SparkQA
commented
Apr 7, 2021
Test build #136991 has finished for PR 32061 at commit
|
SparkQA
commented
Jun 2, 2021
Kubernetes integration test starting |
SparkQA
commented
Jun 2, 2021
Kubernetes integration test status failure |
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
What changes were proposed in this pull request?
This PR refactor #29695, it has some limitations in terms of implementation and abstraction:
countAVGin case of multiple partitions, and actually the current implementation is wrong even in single partition.sum(if()).see the discussion here, The SPIP PDF could be viewed here.
Why are the changes needed?
for better performance
Does this PR introduce any user-facing change?
No
How was this patch tested?
using tests from #29695