Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17141
**[Test build #74843 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74843/testReport)**
for PR 17141 at commit
Github user CodingCat commented on the issue:
https://github.com/apache/spark/pull/14617
ah...somehow I missed this email.
I like this idea, the comments here would be that `if the last screenshot
is the latest design, will the user have to sum up the total amount of used
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/17286
@ioana-delaney Thanks for the replies.
> Given A J1 B J2 C: - case 1
⢠level 0: (A), (B), (C)
⢠level 1: {A, B}, ~~{A, C}~~, {B, C}
⢠level 3: {A, B, C}
Given A J1 B J2
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/17335#discussion_r106828435
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkHadoopUtil.scala
---
@@ -353,6 +354,25 @@ class SparkHadoopUtil extends Logging {
}
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17352
@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, or
Github user ioana-delaney commented on the issue:
https://github.com/apache/spark/pull/15363
@gatorsmile @cloud-fan I rewrote the test cases to align to the join
reorder suite. Please take a look. Thanks.
---
If your project is set up for it, you can reply to this email and have
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/15363#discussion_r106828049
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/joins.scala
---
@@ -20,19 +20,347 @@ package
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17141
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74841/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17141
**[Test build #74841 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74841/testReport)**
for PR 17141 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17141
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/17141
**[Test build #74841 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74841/testReport)**
for PR 17141 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17352
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74839/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17352
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/15363
**[Test build #74842 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74842/testReport)**
for PR 15363 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17352
**[Test build #74839 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74839/testReport)**
for PR 17352 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/17338
@gatorsmile I have merge this pr with master and revert #17290, and
waiting for the jenkins to test
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17338
**[Test build #74840 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74840/testReport)**
for PR 17338 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/14617
Thanks @squito , finally get someone's attention :). I will update the code
soon.
Before this change off-heap on on-heap memory are added together
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17352
**[Test build #74839 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74839/testReport)**
for PR 17352 at commit
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/17352
Miss backslash in python code
## What changes were proposed in this pull request?
Add backslash for line continuation in python code.
## How was this patch tested?
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/17014
@hhbyyh I think I misunderstood your comments in jira. I will update this
pr with the new plan: directly add `protected var storageLevel` in `Predictor`,
without adding setter and getter of it
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/17338
ok, let me do it~
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17338
**[Test build #74838 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74838/testReport)**
for PR 17338 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
Can you revert the changes made in
https://github.com/apache/spark/pull/17290? Then, we can see how many tests
still failed after the existing fixes.
---
If your project is set up for it, you
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17290
After removing the changes in this PR, the test case passed in my local
environment. I think we need to revert it back.
---
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/16971
**[Test build #74837 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74837/testReport)**
for PR 16971 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/17338
@gatorsmile we can find all the test failed here [maven test
result](https://spark-tests.appspot.com/builds/spark-master-test-maven-hadoop-2.7/2799)
---
If your project is set up for it, you can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17338
**[Test build #74836 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74836/testReport)**
for PR 17338 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17331
**[Test build #74835 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74835/testReport)**
for PR 17331 at commit
Github user lw-lin commented on the issue:
https://github.com/apache/spark/pull/17346
@zsxwing would you take a look at this? 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17290
As found in https://github.com/apache/spark/pull/17338, I am afraid this
one caused the following test failure.
- proactive block replication - 4 replicas - 3 block manager deletions
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/17331
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 so, or
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
ok... It was stopped at Spark Core this time. Let me see which PR in Spark
Core was merged recently.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
@sethah Don't worry, I will update code ASAP and @yanboliang will also help
review it. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17338
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74834/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17338
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/17338
**[Test build #74834 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74834/testReport)**
for PR 17338 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17338
**[Test build #74834 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74834/testReport)**
for PR 17338 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
Let us see which cases still 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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
Sorry, I did not realize we have such a JIRA. We just hit it in another PR
and simply fix it. Thanks!
Originally, I thought it was trivial, and thus I did not open a separate
JIRA.
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17338
@srowen I think #17344 was intended to be for a different JIRA and was
accidentally assigned the same JIRA# as this PR (although they are related
issues).
---
If your project is set up for
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17344
Also @gatorsmile don't forget to update the corresponding JIRA when you
merge a PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/17302
cc @cloud-fan
---
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
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17344
It looks like this has the wrong JIRA id and should be SPARK-19988? I've
marked that jira as resolved by this PR, but let me know if I've misunderstood
things here.
---
If your project is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16596
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/16596
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74833/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16596
**[Test build #74833 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74833/testReport)**
for PR 16596 at commit
Github user budde commented on the issue:
https://github.com/apache/spark/pull/17250
@brkyvz A conference took up a lot of my time last week but I should have
it updated later today
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17179
---
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 tdas commented on the issue:
https://github.com/apache/spark/pull/17179
I am merging this to master in the interest of time. If there are comments,
I will address them in a follow up PR.
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17344
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17344
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74829/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17344
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/17344
**[Test build #74829 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74829/testReport)**
for PR 17344 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17302
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74830/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17302
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/17302
**[Test build #74830 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74830/testReport)**
for PR 17302 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17351
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/17351
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74832/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17351
**[Test build #74832 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74832/testReport)**
for PR 17351 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16596
**[Test build #74833 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74833/testReport)**
for PR 16596 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16596
Jenkins, 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17351
**[Test build #74832 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74832/testReport)**
for PR 17351 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17351
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/17351
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74831/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17351
**[Test build #74831 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74831/testReport)**
for PR 17351 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74828/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14615
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/14615
**[Test build #74828 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74828/testReport)**
for PR 14615 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17191
We already have `group-by.sql` and `group-by-ordinal.sql`. Could you move
the test cases there?
You can use the following command to turn the conf off or on.
```
-- turn off
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17191#discussion_r106814663
--- Diff: sql/core/src/test/resources/sql-tests/inputs/group-by.sql ---
@@ -35,3 +35,6 @@ FROM testData;
-- Aggregate with foldable input and
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17191#discussion_r106814321
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -2598,4 +2598,27 @@ class SQLQuerySuite extends QueryTest with
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17191
Could you add the related test case? Below is some examples
```Scala
withSQLConf(SQLConf.GROUP_BY_ALIASES_ENABLED.key -> "true",
SQLConf.GROUP_BY_ORDINAL.key -> "true") {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17351
**[Test build #74831 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74831/testReport)**
for PR 17351 at commit
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/17351
[SPARK-20020][SPARKR] DataFrame checkpoint API
## What changes were proposed in this pull request?
Add checkpoint, setCheckpointDir API to R
## How was this patch tested?
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
@windpiger This becomes a general issue for the test cases. Could you
create a separate function `withXYZ` for it? We can reuse it later.
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17302
**[Test build #74830 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74830/testReport)**
for PR 17302 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17338#discussion_r106813669
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/command/DDLSuite.scala
---
@@ -700,20 +701,33 @@ abstract class DDLSuite extends
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16330
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/16330
merged to master and branch-2.1
thanks @shivaram @gatorsmile @cloud-fan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17344
**[Test build #74829 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74829/testReport)**
for PR 17344 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
test 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 so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
Let us run the SBT build too.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
No idea. We need to monitor the mvn builds more closely. This flaky test
case also impacts the sbt build.
Let me merge this first. Then, we can continue to clean the others.
---
If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17349
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/16596
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17338
@srowen It sounds like we did not monitor the mvn testing results. Thus, we
accumulate multiple failures. We need to resolve it one by one.
---
If your project is set up for it, you can reply
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17349
merged. 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
enabled and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14615
**[Test build #74828 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74828/testReport)**
for PR 14615 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/17274
I closed and reopened this PR to trigger the appveyor test.
---
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
Github user yanboliang closed the pull request at:
https://github.com/apache/spark/pull/17274
---
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 yanboliang reopened a pull request:
https://github.com/apache/spark/pull/17274
[SPARK-19925][SPARKR] Fix SparkR spark.getSparkFiles fails when it was
called on executors.
## What changes were proposed in this pull request?
SparkR ```spark.getSparkFiles``` fails when
Github user michalsenkyr commented on a diff in the pull request:
https://github.com/apache/spark/pull/16541#discussion_r106810993
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects/objects.scala
---
@@ -589,6 +590,170 @@ case class MapObjects
Github user michalsenkyr commented on a diff in the pull request:
https://github.com/apache/spark/pull/16541#discussion_r106810940
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/benchmark/SequenceBenchmark.scala
---
@@ -0,0 +1,74 @@
+/*
+ * Licensed to
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17350
Could you add tests?
---
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/17274#discussion_r106810830
--- Diff: R/pkg/inst/tests/testthat/test_context.R ---
@@ -177,6 +177,13 @@ test_that("add and get file to be downloaded with
Spark job on every node",
Github user michalsenkyr commented on a diff in the pull request:
https://github.com/apache/spark/pull/16541#discussion_r106810789
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects/objects.scala
---
@@ -589,6 +590,170 @@ case class MapObjects
101 - 200 of 319 matches
Mail list logo
