Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14580
**[Test build #63545 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63545/consoleFull)**
for PR 14580 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63546/consoleFull)**
for PR 14568 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13868
OK, if you're willing to go one more round and prepare a patch for 2.0, it
would be much appreciated. You're close to the change and I know several people
hit this with 2.0.0. I will revert my
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63544 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63544/consoleFull)**
for PR 14567 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14579
cc @davies
---
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 junyangq commented on a diff in the pull request:
https://github.com/apache/spark/pull/14522#discussion_r74289056
--- Diff: R/pkg/R/DataFrame.R ---
@@ -2121,7 +2121,7 @@ setMethod("arrange",
})
#' @rdname arrange
-#' @name orderBy
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14551#discussion_r74276891
--- Diff: core/src/test/scala/org/apache/spark/util/UtilsSuite.scala ---
@@ -874,4 +874,38 @@ class UtilsSuite extends SparkFunSuite with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14558
**[Test build #63547 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63547/consoleFull)**
for PR 14558 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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 davies commented on the issue:
https://github.com/apache/spark/pull/13701
Merging this into master and 2.0, 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 dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/14583
[SPARK-16994][SQL] PushDownPredicate should not ignore limits.
## What changes were proposed in this pull request?
Currently, `filter` and `limit` are illegally permuted because
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63536/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
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/14568
**[Test build #63543 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63543/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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 nchammas commented on the issue:
https://github.com/apache/spark/pull/14579
None of our options seems great, but if I had to rank them I would say:
1. Add new `Persisted...` classes.
2. Make no changes.
3. Add separate `persisted()` or `cached()` utility
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14522
**[Test build #63549 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63549/consoleFull)**
for PR 14522 at commit
Github user avulanov commented on the issue:
https://github.com/apache/spark/pull/13868
@srowen It seems that the issue is with the new version of `warehousePath`.
It did string replace `user.dir` in the path in the original 2.0.
`warehousePath` was simplified in master due to new
Github user avulanov commented on the issue:
https://github.com/apache/spark/pull/13868
@srowen OK, I think I can do that. Do I understand correctly, that I need
to clone 2.0, make the necessary changes and then make a new PR?
---
If your project is set up for it, you can reply to
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13868
Yeah, you'd branch from branch-2.0, cherry-pick your original PR, resolve
the conflicts as needed, and then open a new PR.
---
If your project is set up for it, you can reply to this email and have
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/14551#discussion_r74276138
--- Diff: core/src/test/scala/org/apache/spark/util/UtilsSuite.scala ---
@@ -874,4 +874,38 @@ class UtilsSuite extends SparkFunSuite with
Github user nchammas commented on the issue:
https://github.com/apache/spark/pull/14579
Ah, you're right.
So if we want to avoid needing magic methods in the main RDD/DataFrame
classes and avoid needing a separate utility method like `cache()`, I think one
option available
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63536 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63536/consoleFull)**
for PR 14567 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63543 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63543/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63543/
Test FAILed.
---
Github user GraceH commented on a diff in the pull request:
https://github.com/apache/spark/pull/14559#discussion_r74278231
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -447,7 +447,11 @@ final class DataFrameWriter[T] private[sql](ds:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14583
**[Test build #63548 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63548/consoleFull)**
for PR 14583 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14452
We reuse all exchanges (including shuffled ones), see this rule:
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/exchange/Exchange.scala#L69-L94
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
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/14546
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63528/
Test PASSed.
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14573#discussion_r74239358
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkPlan.scala ---
@@ -333,15 +333,14 @@ abstract class SparkPlan extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14397
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/14397
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63529/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14159
**[Test build #3211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3211/consoleFull)**
for PR 14159 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13868
It's weird. Some branch 2.0 tests fail in core, but with no visible error
anywhere. But I spotted this failure:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14397
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 viirya commented on the issue:
https://github.com/apache/spark/pull/14452
Originally I use the analyzed logical plans to compare subqueries when
finding the subqueries with the same results. But I think that optimized plan
might be better because it should have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14581
**[Test build #63538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63538/consoleFull)**
for PR 14581 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12896
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63535/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63539 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63539/consoleFull)**
for PR 14568 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/14346
ping @mengxr @shivaram
---
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/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63541/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63541 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63541/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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/14397
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63526/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14397
**[Test build #63526 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63526/consoleFull)**
for PR 14397 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14534
**[Test build #63531 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63531/consoleFull)**
for PR 14534 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14452
@viirya I have taken a look. It looks pretty cool what you are doing. One
question: why are you focussing on CTE's only? Shouldn't we look at any part of
the query tree?
The other thing
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
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 viirya commented on the issue:
https://github.com/apache/spark/pull/14452
@hvanhovell Thanks for looking at this.
The first attempt of this PR is to address all `SubqueryAlias`. But looks
like we use `SubqueryAlias` plan in many places. To de-duplicating all of
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63534 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63534/consoleFull)**
for PR 14567 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14534
**[Test build #63531 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63531/consoleFull)**
for PR 14534 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14534
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/14534
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63531/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14546
**[Test build #63528 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63528/consoleFull)**
for PR 14546 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63537/consoleFull)**
for PR 14568 at commit
GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/14581
Correct example value for spark.ssl.YYY.XXX settings
Docs adjustment to:
- link to other relevant section of docs
- correct statement about the only value when actually other values are
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63540/consoleFull)**
for PR 14568 at commit
GitHub user lalinsky opened a pull request:
https://github.com/apache/spark/pull/14582
[SPARK-16997][SQL] Allow loading of JSON float values as TimestampType
## What changes were proposed in this pull request?
This allows loading JSON like `{"ts": 1470840303.636409}`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63527/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14564
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 this feature
enabled and wishes so, or if the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63533 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63533/consoleFull)**
for PR 14567 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63534/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
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/14567
**[Test build #63534 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63534/consoleFull)**
for PR 14567 at commit
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/14563
Agreed that it's better to avoid tiny PRs for typos where possible, though
when I'm doing something in the moment and encounter a typo I'd rather submit
at least _some_ PR rather than break my
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63536 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63536/consoleFull)**
for PR 14567 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14581
OK
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13701
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63532/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13701
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/14568
**[Test build #63542 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63542/consoleFull)**
for PR 14568 at commit
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/14566
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, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12896
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/12896
**[Test build #63535 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63535/consoleFull)**
for PR 12896 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63539/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63539/consoleFull)**
for PR 14568 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13701
**[Test build #63532 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63532/consoleFull)**
for PR 13701 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14582
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 MLnick commented on the issue:
https://github.com/apache/spark/pull/14579
@nchammas I looked at the `@contextmanager` decorator. It is an easy way to
create a method that returns a context manager, but is is essentially _only_
usable in a `with` statement as it returns a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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 srowen commented on the issue:
https://github.com/apache/spark/pull/14567
Jenkins 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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14567
Jenkins add to whitelist
---
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/13701
**[Test build #63532 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63532/consoleFull)**
for PR 13701 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14577
Hm, I also don't quite like this change, as it's kind of hackily rewriting
dates in Javascript. I am not sure this is correct, even. What does the Spark
job page do to format dates? Seems like it
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14452
@hvanhovell Got it. Thanks for the cue.
I think the thought is the same, to reuse the results of the plans wit same
results.
The performance gain of this PR is from the reuse of the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63537 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63537/consoleFull)**
for PR 14568 at commit
Github user avulanov commented on the issue:
https://github.com/apache/spark/pull/13868
@srowen Could you give me a link to the log of the failed 2.0 build?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63540/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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/14568
**[Test build #63540 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63540/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14555
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/14555
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63530/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14555
**[Test build #63530 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63530/consoleFull)**
for PR 14555 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14546
**[Test build #63527 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63527/consoleFull)**
for PR 14546 at commit
Github user andreweduffy closed the pull request at:
https://github.com/apache/spark/pull/14159
---
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 viirya commented on the issue:
https://github.com/apache/spark/pull/13701
@davies Due to the accumulators for vectorized setting "true" and "false"
are with the same names "numRowGroups", the API looking for the accumulator
will return one among them. So the test becomes
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14159
Yep, closing now
---
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/12896
**[Test build #63535 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63535/consoleFull)**
for PR 12896 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14397
**[Test build #63529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63529/consoleFull)**
for PR 14397 at commit
1 - 100 of 724 matches
Mail list logo
