Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3040 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3040/consoleFull)**
for PR 13498 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13498
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59932/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13498
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 inouehrs commented on the issue:
https://github.com/apache/spark/pull/13446
Since the new encoder framework ([SPARK-15494]) has been merged, my bug fix
part is no longer needed.
I appreciate if the new test case part can be merged. Thanks!
---
If your project is set
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13061
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/13454
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/13498
**[Test build #59937 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59937/consoleFull)**
for PR 13498 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/13418
whoops triggered a build on this one... sorry about that
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #59932 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59932/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13496
**[Test build #59931 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59931/consoleFull)**
for PR 13496 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3044 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3044/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13418
**[Test build #3045 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3045/consoleFull)**
for PR 13418 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3046 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3046/consoleFull)**
for PR 13498 at commit
Github user cloud-fan closed the pull request at:
https://github.com/apache/spark/pull/11632
---
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/13498
**[Test build #3047 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3047/consoleFull)**
for PR 13498 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/13454
ok as this seems to be failing quite commonly in some envs I'm going to
merge this since it fixes the issue, but open to more feedback.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3049 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3049/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13499
**[Test build #59938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59938/consoleFull)**
for PR 13499 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13475
Merging to master / 2.0.
---
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 tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/13492#discussion_r65732323
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/rules.scala
---
@@ -78,8 +78,8 @@ private[sql] object
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13446
**[Test build #59936 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59936/consoleFull)**
for PR 13446 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13446
**[Test build #59939 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59939/consoleFull)**
for PR 13446 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13454
---
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 subrotosanyal opened a pull request:
https://github.com/apache/spark/pull/13499
SPARK-15754 Not letting the credentials containing hdfs delegation tokens
to be added in current user credential.
## What changes were proposed in this pull request?
The credentials are
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13454
**[Test build #59935 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59935/consoleFull)**
for PR 13454 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3043 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3043/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3039/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3038 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3038/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3041 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3041/consoleFull)**
for PR 13498 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13487
Thank you, @rxin .
---
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 ioana-delaney commented on the issue:
https://github.com/apache/spark/pull/13418
@cloud-fan Thank you.
---
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/13498
**[Test build #3048 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3048/consoleFull)**
for PR 13498 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/8559
@skonto I just merged https://github.com/apache/spark/pull/13454, please
let me know if that does not address the issue.
---
If your project is set up for it, you can reply to this email and have
Github user inouehrs commented on the issue:
https://github.com/apache/spark/pull/13446
I reverted the file mode change. Thank you!
---
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/13475
---
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 wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13476#discussion_r65742476
--- Diff: R/pkg/R/column.R ---
@@ -151,6 +151,40 @@ setMethod("substr", signature(x = "Column"),
column(jc)
})
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13496
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59931/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13496
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/13061
**[Test build #59934 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59934/consoleFull)**
for PR 13061 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13454
**[Test build #59933 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59933/consoleFull)**
for PR 13454 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13061
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59934/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13454
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59933/
Test PASSed.
---
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/13483
@viirya Based on my understanding, we want to avoid having duplicate output
columns generated by our APIs. If users want to explicitly have two duplicate
output columns, they can specify them in
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13446
can you revert the file mode change? the test LGTM
---
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
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/13483
@gatorsmile Thanks a lot for your explanation. I agree that if we
internally generate the aggregate expressions that is different than user
specified one , then we should eliminate the
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13499
ok to 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 not have this feature
enabled and wishes so, or if the
Github user squito commented on the issue:
https://github.com/apache/spark/pull/13454
merged 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 wishes so, or
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13499
@subrotosanyal could you update the title to follow the convention?
`[SPARK-][yarn] Summary.` Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #59937 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59937/consoleFull)**
for PR 13498 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13469#discussion_r65746393
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects/objects.scala
---
@@ -519,7 +519,7 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3049 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3049/consoleFull)**
for PR 13498 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13499#discussion_r65752132
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -21,9 +21,13 @@ import
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13115
**[Test build #3052 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3052/consoleFull)**
for PR 13115 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13484
**[Test build #59946 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59946/consoleFull)**
for PR 13484 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13318
**[Test build #59949 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59949/consoleFull)**
for PR 13318 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13476
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59948/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13476
**[Test build #59948 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59948/consoleFull)**
for PR 13476 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13476
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/13494
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59940/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13494
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12313#discussion_r65759591
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/InsertIntoHiveTableSuite.scala
---
@@ -284,8 +284,128 @@ class InsertIntoHiveTableSuite
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13418
thanks, merging to master and 2.0!
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13499#discussion_r65764703
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -64,7 +68,7 @@ private[spark] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3054 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3054/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3053 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3053/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3055 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3055/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3056 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3056/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #59953 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59953/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3057 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3057/consoleFull)**
for PR 13498 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3058 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3058/consoleFull)**
for PR 13498 at commit
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/13481
Yeah actually looking at it the Scala side is a bit ugly. We can make it
prettier there and then just call into it from PySpark, e.g.
```
scala> val formula = new
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13061
> Feel that it would be better to error out rather than running an unknown
version
I meant a null check so you could throw a proper exception instead of a
generic `NullPointerException`.
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/13498
Seems to be related to the sequence in which tests are executed... Perhaps
`src` is changed during tests.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user andrewor14 commented on the issue:
https://github.com/apache/spark/pull/13490
Sounds good. I've updated the 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 feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13490
**[Test build #59954 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59954/consoleFull)**
for PR 13490 at commit
Github user subrotosanyal commented on a diff in the pull request:
https://github.com/apache/spark/pull/13499#discussion_r65762991
--- Diff:
yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -64,7 +68,7 @@ private[spark] class
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13061
> Aren't we already doing that
No, you're throwing a generic exception that doesn't explain what's wrong.
None of the existing errors say "properties file not found", which is what a
null
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13498
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59937/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13469
**[Test build #59941 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59941/consoleFull)**
for PR 13469 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/13491
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 and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13498
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 subrotosanyal commented on the issue:
https://github.com/apache/spark/pull/13499
@vanzin
Updated the title.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13483
I don't think it's a big problem. After users understand the semantic, they
can easily work around it, by not putting grouping columns in agg list, or
turning off the config.
Well, it looks
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/13469
LGTM pending Jenkins.
---
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/13070
@cloud-fan Thank you for your review! Just quickly added the space.
---
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
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/13484
LGTM too, probably this will be even more of a improvement once we get the
other bottlenecks fixed
---
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/13446
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/13446
**[Test build #59936 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59936/consoleFull)**
for PR 13446 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13061
Two nits that I missed before and this is good to go.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3050 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3050/consoleFull)**
for PR 13498 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13446
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59936/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13498
**[Test build #3044 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3044/consoleFull)**
for PR 13498 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13269
yea, but may not happen before 2.0. It needs some more refactor to the
object operator execution model. For example, the serializer in `AppendColumns`
has no corresponding attribute, its input is
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13318#discussion_r65754375
--- Diff:
core/src/main/java/org/apache/spark/unsafe/map/BytesToBytesMap.java ---
@@ -221,7 +221,8 @@ public BytesToBytesMap(
SparkEnv.get() !=
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/13491
LGTM provided tests still pass
---
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/13499
**[Test build #59938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59938/consoleFull)**
for PR 13499 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13499
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59938/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13499
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/13401
**[Test build #59944 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59944/consoleFull)**
for PR 13401 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13061#discussion_r65747950
--- Diff: core/src/main/scala/org/apache/spark/package.scala ---
@@ -41,7 +41,53 @@ package org.apache
* level interfaces. These are subject to changes
1 - 100 of 568 matches
Mail list logo
