Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220300237
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/13195#issuecomment-220300140
**[Test build #58863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58863/consoleFull)**
for PR 13195 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220300239
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/13194#issuecomment-220298609
**[Test build #58864 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58864/consoleFull)**
for PR 13194 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220293067
**[Test build #58863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58863/consoleFull)**
for PR 13195 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220290553
**[Test build #58862 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58862/consoleFull)**
for PR 13195 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220290559
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/13195#issuecomment-220290555
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/13195#issuecomment-220290258
**[Test build #58862 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58862/consoleFull)**
for PR 13195 at commit
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220289944
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220289627
**[Test build #58861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58861/consoleFull)**
for PR 13195 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220289638
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/13195#issuecomment-220289634
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13195#discussion_r63856396
--- Diff: python/pyspark/ml/evaluation.py ---
@@ -193,9 +193,7 @@ class RegressionEvaluator(JavaEvaluator, HasLabelCol,
HasPredictionCol):
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13195#discussion_r63856481
--- Diff: python/pyspark/ml/evaluation.py ---
@@ -270,7 +268,7 @@ class MulticlassClassificationEvaluator(JavaEvaluator,
HasLabelCol, HasPredictio
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13195#issuecomment-220289317
**[Test build #58861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58861/consoleFull)**
for PR 13195 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/13195
[Minor] [ML] [PySpark] ml.evaluation Scala and Python API sync
## What changes were proposed in this pull request?
```ml.evaluation``` Scala and Python API sync.
## How was this
Github user l15k4 commented on the pull request:
https://github.com/apache/spark/pull/13092#issuecomment-220288584
Hey, I wanted to give a shot to spark 2.0 preview, what is the best way to
get the dependency?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13194#issuecomment-220287181
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/13194#issuecomment-220287182
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/13194#issuecomment-220287155
**[Test build #58860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58860/consoleFull)**
for PR 13194 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13193#issuecomment-220286446
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/13193#issuecomment-220286448
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/13193#issuecomment-220286214
**[Test build #58857 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58857/consoleFull)**
for PR 13193 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13194#issuecomment-220285295
**[Test build #58860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58860/consoleFull)**
for PR 13194 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/13194
[SPARK-15402] [ML] [PySpark] PySpark ml.evaluation should support save/load
## What changes were proposed in this pull request?
Since ```ml.evaluation``` has supported save/load at Scala
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13187#issuecomment-220281464
@srowen Actually I asked @cloud-fan about this in
https://github.com/apache/spark/pull/12858#issuecomment-220207574. It seems (If
I understood correctly) we should
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13191#issuecomment-220279912
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/13191#issuecomment-220279910
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/13191#issuecomment-220279764
**[Test build #58858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58858/consoleFull)**
for PR 13191 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220278856
**[Test build #58859 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58859/consoleFull)**
for PR 13186 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220278544
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13187#issuecomment-220278337
Heh, yeah I had exactly the same change lined up in a pull request. LGTM.
But there are more instances of internal usage of the old API that can be
updated. Look for
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13190#issuecomment-220277518
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13168
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/13168#issuecomment-220277041
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12951#issuecomment-220276101
cc @kayousterhout for review
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/13105#issuecomment-220275858
cc @cloud-fan / @liancheng
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13192#issuecomment-220274969
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/13192#issuecomment-220274966
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/13192#issuecomment-220274764
**[Test build #58855 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58855/consoleFull)**
for PR 13192 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13142#issuecomment-220274169
Is this mostly moving test cases around? Any idea why the diff is so large?
This makes it very difficult to review.
---
If your project is set up for it, you can reply
Github user DoingDone9 commented on the pull request:
https://github.com/apache/spark/pull/13130#issuecomment-220273234
I refer to other codes using the maximumSize method @akohli
```
/** A cache of Spark SQL data source tables that have been accessed. */
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/13168#issuecomment-220272524
ping @srowen
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/13192#issuecomment-220272109
cc @sameeragarwal / @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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13191#issuecomment-220270951
**[Test build #58858 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58858/consoleFull)**
for PR 13191 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13191#issuecomment-220270668
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220270478
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9759#issuecomment-220270486
Hm, I know that Hadoop libs use Jackson 2.4. Including and using a later
version can mostly work, especially if Spark code doesn't use APIs from later
versions. I think
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220270481
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/13186#issuecomment-220270298
**[Test build #58854 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58854/consoleFull)**
for PR 13186 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13193#issuecomment-220267483
**[Test build #58857 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58857/consoleFull)**
for PR 13193 at commit
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/13193
[SPARK-15400][SQL][MINOR] CreateNamedStruct and CreateNamedStructUnsafe
should preserve metadata of value expressions if it is NamedExpression.
## What changes were proposed in this pull request?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12004#issuecomment-220265675
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/12004#issuecomment-220265664
**[Test build #58856 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58856/consoleFull)**
for PR 12004 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12004#issuecomment-220265671
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/12004#issuecomment-220265269
**[Test build #58856 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58856/consoleFull)**
for PR 12004 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-220263980
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/13170#issuecomment-220263982
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/13170#issuecomment-220263742
**[Test build #58853 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58853/consoleFull)**
for PR 13170 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13163#issuecomment-220261449
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/13163#issuecomment-220261272
**[Test build #58852 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58852/consoleFull)**
for PR 13163 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13163#issuecomment-220261453
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user WeichenXu123 commented on the pull request:
https://github.com/apache/spark/pull/13172#issuecomment-220260517
@srowen
Modified as you expected.
---
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 closed the pull request at:
https://github.com/apache/spark/pull/12840
---
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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13192#issuecomment-220257517
Hi, @rxin .
This is the first attempt according to your request.
I removed some obsolete code in #11019 in order to pass the tests.
Please let me know
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-220256852
Thank you so much, @cloud-fan !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13192#issuecomment-220256665
**[Test build #58855 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58855/consoleFull)**
for PR 13192 at commit
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/13057#issuecomment-220256566
@srowen
See if I have addressed all your comments.
---
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 dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/13192
[SPARK-13135][SQL] Don't print expressions recursively in generated code
## What changes were proposed in this pull request?
This PR is an up-to-date and a little bit improved
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/11601#issuecomment-220254380
@hhbyyh really sorry this slipped in the rush around 2.0 QA. I'm afraid it
will have to be revisited after 2.0 release! But I think it should be in good
shape to merge
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-220254151
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12719
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10125#discussion_r63835534
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DecimalType.scala ---
@@ -109,6 +109,7 @@ object DecimalType extends AbstractDataType {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220251693
**[Test build #58854 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58854/consoleFull)**
for PR 13186 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220250927
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220250743
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/13186#issuecomment-220250746
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/13186#issuecomment-220250574
**[Test build #58849 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58849/consoleFull)**
for PR 13186 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13186#issuecomment-220249847
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/13186#issuecomment-220249844
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/13186#issuecomment-220249656
**[Test build #58847 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58847/consoleFull)**
for PR 13186 at commit
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/13191#issuecomment-22024
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-220246020
**[Test build #58853 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58853/consoleFull)**
for PR 13170 at commit
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13170#discussion_r63832125
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -271,6 +274,54 @@ case class LoadData(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13191#issuecomment-220244417
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
Github user pravingadakh commented on the pull request:
https://github.com/apache/spark/pull/13191#issuecomment-220244160
cc @dbtsai
---
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 pravingadakh opened a pull request:
https://github.com/apache/spark/pull/13191
[SPARK-14613][ML] Add @Since into the matrix and vector classes in
spark-mllib-local
## What changes were proposed in this pull request?
This PR add `@Since` annotations in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13090#issuecomment-220243696
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/13163#issuecomment-220243685
**[Test build #58852 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58852/consoleFull)**
for PR 13163 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13090#issuecomment-220243699
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/13090#issuecomment-220243516
**[Test build #58846 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58846/consoleFull)**
for PR 13090 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13045#issuecomment-220242854
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/13045#issuecomment-220242851
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/13045#issuecomment-220242701
**[Test build #58850 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58850/consoleFull)**
for PR 13045 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13135
---
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 MLnick commented on the pull request:
https://github.com/apache/spark/pull/13135#issuecomment-220241901
LGTM too. Merged to master/branch-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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220241617
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/13188#issuecomment-220241614
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/13188#issuecomment-220241461
**[Test build #58844 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58844/consoleFull)**
for PR 13188 at commit
701 - 800 of 811 matches
Mail list logo
