Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11410#issuecomment-193653823
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11410#issuecomment-193653822
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193651401
**[Test build #52644 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52644/consoleFull)**
for PR 11514 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193651407
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193651406
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193650798
**[Test build #2619 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2619/consoleFull)**
for PR 11514 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11505#issuecomment-193650717
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193650362
**[Test build #52644 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52644/consoleFull)**
for PR 11514 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11505#issuecomment-193649424
OK, well unless there's a moderately strong objection, I think we can go
ahead and merge this, even for 1.6. It's a cheap defensive measure and I don't
see a downside.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193648651
**[Test build #2619 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2619/consoleFull)**
for PR 11514 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11443#issuecomment-193648680
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11443#issuecomment-193648669
**[Test build #52642 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52642/consoleFull)**
for PR 11443 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11443#issuecomment-193648682
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11403#issuecomment-193647799
**[Test build #52643 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52643/consoleFull)**
for PR 11403 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193647377
**[Test build #2618 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2618/consoleFull)**
for PR 11514 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/11573#discussion_r55324768
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -0,0 +1,197 @@
+/*
+ * Licensed to the Apache Software
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11403#issuecomment-193647125
@JoshRosen Do you have time to review this?
---
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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11530#issuecomment-193645680
Thank you, @zsxwing .
---
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 pull request:
https://github.com/apache/spark/pull/11501#issuecomment-193643544
**[Test build #52641 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52641/consoleFull)**
for PR 11501 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11443#issuecomment-193643543
**[Test build #52642 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52642/consoleFull)**
for PR 11443 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11514#issuecomment-193642699
**[Test build #2618 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2618/consoleFull)**
for PR 11514 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11501#issuecomment-193642117
**[Test build #2617 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2617/consoleFull)**
for PR 11501 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/11573#discussion_r55324206
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -0,0 +1,197 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11530#issuecomment-193641581
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11501#issuecomment-193641668
**[Test build #52640 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52640/consoleFull)**
for PR 11501 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11530#issuecomment-193641575
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11530#issuecomment-193641123
**[Test build #52631 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52631/consoleFull)**
for PR 11530 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11572#issuecomment-193639421
**[Test build #52639 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52639/consoleFull)**
for PR 11572 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11573#issuecomment-193637484
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11573#issuecomment-193637485
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11501#issuecomment-193637383
Oops there is a conflict.
---
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 pull request:
https://github.com/apache/spark/pull/11573#issuecomment-193637270
**[Test build #52630 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52630/consoleFull)**
for PR 11573 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11501#issuecomment-193637100
**[Test build #2616 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2616/consoleFull)**
for PR 11501 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-193636595
Splitting up `doPut()` into two smaller methods, one concerned with putting
bytes and another for putting iterators of objects, would let me simplify its
return type
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-193636217
**[Test build #52638 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52638/consoleFull)**
for PR 11534 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-193635954
FYI I rebased this to fix the merge conflicts, so the diff + commit log is
now smaller.
---
If your project is set up for it, you can reply to this email and have
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/11444#discussion_r55322763
--- Diff: python/pyspark/sql/types.py ---
@@ -681,6 +681,139 @@ def __eq__(self, other):
for v in [ArrayType, MapType,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11574#issuecomment-193634786
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11574#issuecomment-193634791
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11574#issuecomment-193634426
**[Test build #52633 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52633/consoleFull)**
for PR 11574 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11574#issuecomment-193634399
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11572#issuecomment-193634049
**[Test build #52637 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52637/consoleFull)**
for PR 11572 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11533#issuecomment-193632211
**[Test build #52636 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52636/consoleFull)**
for PR 11533 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11565#issuecomment-193630940
Let me add the test cases in column pruning through `Windows` in
`ColumnPruningSuite` tonight/tomorrow. Thanks!
---
If your project is set up for it, you can reply
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11533#issuecomment-193630155
Conflicts fixed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11572#issuecomment-193628454
**[Test build #52634 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52634/consoleFull)**
for PR 11572 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11016#issuecomment-193628447
**[Test build #52635 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52635/consoleFull)**
for PR 11016 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11565#issuecomment-193628390
ah I see, makes sense. It would be better if there are some tests which
guarantee the column pruning for window still works. Otherwise LGTM.
cc @yhuai
---
If
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11270#issuecomment-193627655
I will take an action as soon as I could have some feedback for this
conflict.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11574#issuecomment-193627008
**[Test build #52633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52633/consoleFull)**
for PR 11574 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/11574
[SPARK-13740][SQL] add null check for _verify_type in types.py
## What changes were proposed in this pull request?
This PR adds null check in `_verify_type` according to the nullability
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11574#issuecomment-193626640
cc @yhuai @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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11406#issuecomment-193626228
**[Test build #52632 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52632/consoleFull)**
for PR 11406 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11533#issuecomment-193619570
LGTM2. There are conflicts now though.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11502
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11502#issuecomment-193618865
LGTM I'm merging this into 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
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/11502#discussion_r55319064
--- Diff: core/src/main/scala/org/apache/spark/storage/DiskStore.scala ---
@@ -54,15 +54,12 @@ private[spark] class DiskStore(blockManager:
BlockManager,
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/11509#discussion_r55318504
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -465,214 +379,165 @@ abstract class OutputWriter {
}
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11565#issuecomment-193616509
We still can prune the child even if we do not have `projectList`. See the
following code:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11555#issuecomment-193616416
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11555#issuecomment-193616413
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11555#issuecomment-193616299
**[Test build #52626 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52626/consoleFull)**
for PR 11555 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11565#issuecomment-193614610
After think about it more, I think the `projectList` maybe useful to do
column pruning for `Window`.
If there is a `Project` above `Window`, it's easy to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11567#issuecomment-193613491
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11567#issuecomment-193613494
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11565#discussion_r55317197
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -345,8 +343,6 @@ object ColumnPruning extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11567#issuecomment-193612972
**[Test build #52627 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52627/consoleFull)**
for PR 11567 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11444#issuecomment-193611600
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11444#issuecomment-193611603
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11444#issuecomment-193611469
**[Test build #52629 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52629/consoleFull)**
for PR 11444 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11530#issuecomment-193611280
**[Test build #52631 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52631/consoleFull)**
for PR 11530 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11573#issuecomment-193610715
Note: The only changes I made on top of #11048 is addressing the
outstanding comments in that patch and some minor clean ups. It's entirely
possible that there
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11530#issuecomment-193610488
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11566
---
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 pull request:
https://github.com/apache/spark/pull/11573#issuecomment-193609366
**[Test build #52630 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52630/consoleFull)**
for PR 11573 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/11573#discussion_r55316476
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -0,0 +1,197 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/11573#discussion_r55316403
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -0,0 +1,197 @@
+/*
+ * Licensed to the Apache Software
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/11563#issuecomment-193609126
@rxin Thanks for the input. Let me try to work on it and see if i encounter
any issues
---
If your project is set up for it, you can reply to this email and have
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11566#issuecomment-193609085
Thanks. Merging to master and 1.6
---
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/11573
[SPARK-13139][SQL] Parse Hive DDL commands ourselves
## What changes were proposed in this pull request?
This patch is ported over from @viirya's changes in #11048. Currently for
most
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193608028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193608023
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11444#discussion_r55316023
--- Diff: python/pyspark/sql/types.py ---
@@ -681,6 +681,139 @@ def __eq__(self, other):
for v in [ArrayType, MapType,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193607352
**[Test build #52623 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52623/consoleFull)**
for PR 11571 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11444#issuecomment-193604622
**[Test build #52629 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52629/consoleFull)**
for PR 11444 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11533#issuecomment-193600272
**[Test build #2615 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2615/consoleFull)**
for PR 11533 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11565#discussion_r55314448
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -345,8 +343,6 @@ object ColumnPruning extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11501#issuecomment-193595713
**[Test build #2616 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2616/consoleFull)**
for PR 11501 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11274
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/11274#issuecomment-193595238
Merging this 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11572#issuecomment-193593900
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11572#issuecomment-193593899
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-193593849
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11572#issuecomment-193593805
**[Test build #52625 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52625/consoleFull)**
for PR 11572 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-193593851
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-193593721
**[Test build #52619 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52619/consoleFull)**
for PR 11550 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11570#issuecomment-193591065
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11570#issuecomment-193591062
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11570#issuecomment-193590521
**[Test build #52622 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52622/consoleFull)**
for PR 11570 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11569#issuecomment-193585812
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
1 - 100 of 748 matches
Mail list logo
