Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/12259#discussion_r60172550
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/linalg/udt/VectorUDT.scala ---
@@ -0,0 +1,103 @@
+/*
+ * Licensed to the Apache Software Foundat
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/12259#discussion_r60172539
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/linalg/udt/MatrixUDT.scala ---
@@ -0,0 +1,108 @@
+/*
+ * Licensed to the Apache Software Foundat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211726625
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211726623
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211726480
**[Test build #56185 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56185/consoleFull)**
for PR 12352 at commit
[`034cb03`](https://g
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12353#issuecomment-211726421
Hi, @rxin . Now, the PR is updated in the following ways.
1. `CaseWhen` split into three classes:
- `CaseWhenBase`: abstract base class
- `Case
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12059#issuecomment-211726085
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12059#issuecomment-211726086
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-211726110
Now the VectorUDT and MatrixUDT tests are moved to mllib.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12059#issuecomment-211725948
**[Test build #56178 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56178/consoleFull)**
for PR 12059 at commit
[`71bebd6`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-211725741
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-211725739
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12353#issuecomment-211725663
**[Test build #56191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56191/consoleFull)**
for PR 12353 at commit
[`a9294bd`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-211725565
**[Test build #56180 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56180/consoleFull)**
for PR 12259 at commit
[`6cdc446`](https://g
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12352#discussion_r60171658
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/FileScanRDD.scala
---
@@ -53,33 +55,74 @@ class FileScanRDD(
override
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12409#issuecomment-211724615
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12409#issuecomment-211724619
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user lw-lin commented on the pull request:
https://github.com/apache/spark/pull/12489#issuecomment-211724261
@zsxwing would you mind taking a look? 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 pr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12409#issuecomment-211724245
**[Test build #56181 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56181/consoleFull)**
for PR 12409 at commit
[`431bccb`](https://g
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/12402#discussion_r60171349
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/clustering/GaussianMixture.scala ---
@@ -105,6 +108,15 @@ class GaussianMixtureModel private[ml] (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211722829
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211722828
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-211722780
**[Test build #56190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56190/consoleFull)**
for PR 12259 at commit
[`85d1df0`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12381#issuecomment-211722776
**[Test build #56189 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56189/consoleFull)**
for PR 12381 at commit
[`5290476`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12491#issuecomment-211722740
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 p
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211722714
**[Test build #56183 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56183/consoleFull)**
for PR 12352 at commit
[`41ae07f`](https://g
GitHub user hujy opened a pull request:
https://github.com/apache/spark/pull/12491
[SPARK-14712][ML]spark.ml.LogisticRegressionModel.toString should sumâ¦
## What changes were proposed in this pull request?
[SPARK-14712](https://issues.apache.org/jira/browse/SPARK-14712)
spa
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211722592
**[Test build #56188 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56188/consoleFull)**
for PR 12473 at commit
[`61b51f2`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211722649
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211722647
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12450#issuecomment-211721783
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12450#issuecomment-211721784
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12450#issuecomment-211721561
**[Test build #56175 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56175/consoleFull)**
for PR 12450 at commit
[`feefa8d`](https://g
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12113#issuecomment-211721515
Looking at this now ... (might take a while though because i'd need to page
in all the details)
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12489#issuecomment-211721474
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12489#issuecomment-211721473
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12489#issuecomment-211721419
**[Test build #56184 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56184/consoleFull)**
for PR 12489 at commit
[`48453fd`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12153#issuecomment-211721311
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12153#issuecomment-211721313
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12153#issuecomment-211721217
**[Test build #56158 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56158/consoleFull)**
for PR 12153 at commit
[`3484559`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12160#issuecomment-211720884
**[Test build #2827 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2827/consoleFull)**
for PR 12160 at commit
[`6ce7e6a`](https://
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12487#issuecomment-211720667
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12487#issuecomment-211720669
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211720533
@jerryshao Yes, what you said is right.
---
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 proj
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12487#issuecomment-211720504
**[Test build #56176 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56176/consoleFull)**
for PR 12487 at commit
[`dab1a24`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-211720350
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-211720356
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211720423
**[Test build #56188 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56188/consoleFull)**
for PR 12473 at commit
[`61b51f2`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-211720038
**[Test build #56179 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56179/consoleFull)**
for PR 12260 at commit
[`954dc6b`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12160#issuecomment-211718852
**[Test build #2825 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2825/consoleFull)**
for PR 12160 at commit
[`6ce7e6a`](https://
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211717311
So my understanding is that actually supporting **different** HDFS other
than default one, not **multiple** HDFS, is that right?
---
If your project is set up for it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12409#issuecomment-211717173
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12409#issuecomment-211717172
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12409#issuecomment-211717003
**[Test build #56177 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56177/consoleFull)**
for PR 12409 at commit
[`cecb83b`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12160#issuecomment-211716750
**[Test build #2826 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2826/consoleFull)**
for PR 12160 at commit
[`6ce7e6a`](https://
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-211716668
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-211716669
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12257#issuecomment-211716554
**[Test build #56172 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56172/consoleFull)**
for PR 12257 at commit
[`f365937`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211716533
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211716518
**[Test build #56186 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56186/consoleFull)**
for PR 12473 at commit
[`59eb03c`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211716532
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12490#issuecomment-211715196
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12490#issuecomment-211715186
**[Test build #56187 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56187/consoleFull)**
for PR 12490 at commit
[`f4161a0`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12490#issuecomment-211715199
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12490#issuecomment-211714809
**[Test build #56187 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56187/consoleFull)**
for PR 12490 at commit
[`f4161a0`](https://gi
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/12487#issuecomment-211714812
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
enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12485#issuecomment-211714387
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12485#issuecomment-211714386
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12485#issuecomment-211714285
**[Test build #56174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56174/consoleFull)**
for PR 12485 at commit
[`75d1115`](https://g
GitHub user ericl opened a pull request:
https://github.com/apache/spark/pull/12490
[SPARK-14724] Use radix sort for shuffles and sort operator when possible
## What changes were proposed in this pull request?
Spark currently uses TimSort for all in-memory sorts, including s
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211714034
**[Test build #56186 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56186/consoleFull)**
for PR 12473 at commit
[`59eb03c`](https://gi
Github user JasonMWhite commented on the pull request:
https://github.com/apache/spark/pull/12470#issuecomment-211712175
After some experimentation on the Scala side, I see that this PR would be a
significant departure from Scala's interface, where the schema and field names
are not f
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12483
---
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 ena
Github user JasonMWhite closed the pull request at:
https://github.com/apache/spark/pull/12470
---
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 i
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12486
---
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 ena
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11865#issuecomment-211711849
Yup go for 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12486#issuecomment-211711705
Merging in 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 featu
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12483#issuecomment-211711447
Merging in master. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have t
Github user rishabhbhardwaj closed the pull request at:
https://github.com/apache/spark/pull/12202
---
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 featu
Github user rishabhbhardwaj commented on the pull request:
https://github.com/apache/spark/pull/12202#issuecomment-211710258
@MLnick : I need to study how MLParam works.For now,I am closing this
PR.You can take this forward.Thanks.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12489#issuecomment-211708315
**[Test build #56184 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56184/consoleFull)**
for PR 12489 at commit
[`48453fd`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211708316
**[Test build #56185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56185/consoleFull)**
for PR 12352 at commit
[`034cb03`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12485#issuecomment-211708134
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12485#issuecomment-211708101
**[Test build #56170 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56170/consoleFull)**
for PR 12485 at commit
[`6019541`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12485#issuecomment-211708135
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211707951
Hi @davies , I have fixed the mistake that may report 0 size for single
file partition, and also catch and handle `ColumnarBatch` specially. I have
verified it locall
GitHub user lw-lin opened a pull request:
https://github.com/apache/spark/pull/12489
[SPARK-14701][Streaming] First stop the event loop, then stop the
checkpoint writer in JobGenerator
## What changes were proposed in this pull request?
The stopping order of the `event loop
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12488#issuecomment-211706576
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 p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12483#issuecomment-211706519
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12483#issuecomment-211706516
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12483#issuecomment-211706217
**[Test build #56169 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56169/consoleFull)**
for PR 12483 at commit
[`91fbca0`](https://g
GitHub user mathieulongtin opened a pull request:
https://github.com/apache/spark/pull/12488
Support single argument version of sqlContext.getConf
## What changes were proposed in this pull request?
In Python, sqlContext.getConf didn't allow getting the system default
(getC
Github user lresende commented on the pull request:
https://github.com/apache/spark/pull/12348#issuecomment-211705986
@JoshRosen All good 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
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/12476#issuecomment-211705461
Thanks, Marcelo. Much appreciated!
---
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 do
Github user nezihyigitbasi commented on the pull request:
https://github.com/apache/spark/pull/11865#issuecomment-211703836
Mima tests failing, I guess we can exclude them all. What do you think?
```Scala
[info] spark-core: found 3 potential binary incompatibilities while
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12352#issuecomment-211703567
**[Test build #56183 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56183/consoleFull)**
for PR 12352 at commit
[`41ae07f`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211703497
**[Test build #56182 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56182/consoleFull)**
for PR 12473 at commit
[`c0374af`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211703519
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12473#issuecomment-211703518
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12486#issuecomment-211703369
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
101 - 200 of 1122 matches
Mail list logo
