GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/16647
[SPARK-19292][SQL] filter with partition columns should be case-insensitive
on Hive tables
## What changes were proposed in this pull request?
When we query a table with a filter on
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16605
The workaround @cloud-fan said is good to me though, IMO the most critical
issue here is that this cast exception happens not in analysis phases but in
runtime. So, at least I think we should modify
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/15505#discussion_r96883996
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -244,32 +245,45 @@ class
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16646
cc @felixcheung
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user scwf commented on the issue:
https://github.com/apache/spark/pull/16633
I think the local limit cost is important, we assume recompute partions
number: m, all the partitions: n
m = 1, n =100 is a positive case, but there also cases that m very close to
n(even m = n).
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16346
merged to master, thanks @jsoltren!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16346
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user scwf commented on the issue:
https://github.com/apache/spark/pull/16633
Your proposal avoid the cost of all partitions compute and shuffle for
local limit but introduce some partitions recompute for local limit stage.
We can not decide which cost is cheaper(in
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16633
@scwf You still don't get the point. Although few partitions need to
recompute in local limit, most of other partitions are saved from computation.
In most cases, it is worth. You can refer to my
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16642
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16642
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71662/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16642
**[Test build #71662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71662/testReport)**
for PR 16642 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16646
**[Test build #71665 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71665/testReport)**
for PR 16646 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/16646
[SPARK-19291][SPARKR][ML] spark.gaussianMixture supports output
log-likelihood.
## What changes were proposed in this pull request?
```spark.gaussianMixture``` supports output total
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71659/
Test PASSed.
---
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16633
@scwf it is fair. anyway, i don't think a proposal can't improve any point
of the issues is worth so many requested changing...
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16552
**[Test build #71659 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71659/testReport)**
for PR 16552 at commit
Github user scwf commented on the issue:
https://github.com/apache/spark/pull/16633
I think before compare our proposals , we should first make sure our
proposal will not bring performance regression.
---
If your project is set up for it, you can reply to this email and have your
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16645
cc @yhuai @gatorsmile
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16645
**[Test build #71663 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71663/testReport)**
for PR 16645 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71664 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71664/testReport)**
for PR 16593 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/16645
[SPARK-19290][SQL] add post-hoc resolution
## What changes were proposed in this pull request?
To implement DDL commands, we added several analyzer rules in sql/hive
module to analyze
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71660/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71660 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71660/testReport)**
for PR 16593 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71657/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71657/testReport)**
for PR 16593 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16644
Yes it is. What error do you get? these examples are compiled with the code
and compiles correctly in master and previous 2.x builds.
---
If your project is set up for it, you can reply to this
Github user ganeshkrishnan1 commented on the issue:
https://github.com/apache/spark/pull/16644
Fails to compile on Spark 2.1.0
Shouldn't mlib be backward compatible?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71656/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71656 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71656/testReport)**
for PR 16593 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16644
Please see http://spark.apache.org/contributing.html first
This is an example for .mllib. While it works with 2.x, or should, it is
not intended to use SparkSession, as I understand.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16644
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
GitHub user getintouchapp opened a pull request:
https://github.com/apache/spark/pull/16644
Update LDAExample with Spark 2.1.0
Changes: Updated code with new Spark 2.x changes
Removed SparkContext and replaced with Spark Session
Fixed compile time errors in new Spark
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16028
**[Test build #71661 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71661/testReport)**
for PR 16028 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71658/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16028
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16028
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16028
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71661/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16028
**[Test build #71658 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71658/testReport)**
for PR 16028 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16593
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71655/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71655 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71655/testReport)**
for PR 16593 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16593
good catch! introducing a new analyzer rule SGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16571
In the jira, we decide to optimize MultivariateOnlineSummarizer first, so
this pr will be closed.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user zhengruifeng closed the pull request at:
https://github.com/apache/spark/pull/16571
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user lins05 commented on the issue:
https://github.com/apache/spark/pull/16593
I just found "create table using hive " (without "select ... from", i.e.
the non-CTAS form) is handled by `CreateTableCommand`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16642
**[Test build #71662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71662/testReport)**
for PR 16642 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16642
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16642
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16642
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71645/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16642
**[Test build #71645 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71645/testReport)**
for PR 16642 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16028
**[Test build #71661 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71661/testReport)**
for PR 16028 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16593#discussion_r96849182
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveDDLSuite.scala
---
@@ -1384,4 +1394,96 @@ class HiveDDLSuite
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71660 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71660/testReport)**
for PR 16593 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16552
**[Test build #71659 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71659/testReport)**
for PR 16552 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16635
thanks, merging to master!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16028
**[Test build #71658 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71658/testReport)**
for PR 16028 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16635
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71653/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16552
**[Test build #71653 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71653/testReport)**
for PR 16552 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71657/testReport)**
for PR 16593 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71656 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71656/testReport)**
for PR 16593 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71652/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16552
**[Test build #71652 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71652/testReport)**
for PR 16552 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16496
@cloud-fan, could you take a look please?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12064
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16593
**[Test build #71655 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71655/testReport)**
for PR 16593 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/12064
LGTM, merged into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16631
@gatorsmile That would be great, thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71654/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16552
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16552
**[Test build #71654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71654/testReport)**
for PR 16552 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16611
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16611
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71650/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16611
**[Test build #71650 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71650/testReport)**
for PR 16611 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16643
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71647/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16643
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71648/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16643
**[Test build #71647 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71647/testReport)**
for PR 16643 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #71648 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71648/testReport)**
for PR 15192 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16592
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71651/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16592
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16592
**[Test build #71651 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71651/testReport)**
for PR 16592 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16611
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16611
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71649/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16611
**[Test build #71649 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71649/testReport)**
for PR 16611 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12064
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71646/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12064
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12064
**[Test build #71646 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71646/testReport)**
for PR 12064 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16635
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16635
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71644/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16635
**[Test build #71644 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71644/testReport)**
for PR 16635 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16633
@scwf I understand your point. But the main issue is, you can't save the
local limit cost and the shuffling cost. You still need to process all rows in
all partitions and shuffle (some of) them to
301 - 400 of 448 matches
Mail list logo
