Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/8799#issuecomment-141355072
LGTM Thanks for fixing 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 project does not
Github user FlytxtRnD commented on a diff in the pull request:
https://github.com/apache/spark/pull/6880#discussion_r39827805
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/DpMeans.scala ---
@@ -0,0 +1,247 @@
+/*
+ * Licensed to the Apache Software
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8800#discussion_r39882820
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/hiveUDFs.scala
---
@@ -59,19 +59,52 @@ private[hive] class HiveFunctionRegistry(underlying:
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141520379
@navis can you give us the data type that caused this problem?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8749#issuecomment-141520185
Yes I agree @kmadhugit can you add a java doc to explain the semantics?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141522666
Will split this PR to two PRs.
---
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 yhuai opened a pull request:
https://github.com/apache/spark/pull/8824
[SPARK-10672] [SQL] Do not fail when we cannot save the metadata of a data
source table in a hive compatible way
https://issues.apache.org/jira/browse/SPARK-10672
You can merge this pull request
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/8615#issuecomment-141534364
So I left this running on a machine just to see if it would ever complete,
and it did although:
Finished test(python): pyspark.streaming.tests (762976s)
Finished
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-141534572
Merged build started.
---
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/8825#issuecomment-141537831
[Test build #42680 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42680/consoleFull)
for PR 8825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8768#issuecomment-141540489
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8806#discussion_r39890833
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonSuite.scala
---
@@ -1159,4 +1159,104 @@ class JsonSuite extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8768#issuecomment-141540485
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/8825#issuecomment-141592972
[Test build #42701 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42701/consoleFull)
for PR 8825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8803#issuecomment-141593214
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/8803#issuecomment-141593213
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/8828#issuecomment-141596522
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141596533
Merged build started.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141598105
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user tribbloid commented on the pull request:
https://github.com/apache/spark/pull/8785#issuecomment-141598082
all fixed (except the PR, will fix soon), thanks a lot for pointing them
out!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141598171
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141598186
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141598742
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141598731
Merged build triggered.
---
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/8790#issuecomment-141599258
[Test build #42705 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42705/consoleFull)
for PR 8790 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8831#issuecomment-141601051
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/8831#issuecomment-141601028
[Test build #42698 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42698/console)
for PR 8831 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8831#issuecomment-141601050
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 mingyukim commented on the pull request:
https://github.com/apache/spark/pull/8763#issuecomment-141593054
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8803#issuecomment-141593136
[Test build #42700 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42700/console)
for PR 8803 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141593394
[Test build #42690 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42690/console)
for PR 8828 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8781#discussion_r39911678
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -180,6 +180,38 @@ class StreamingContextSuite extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141598935
[Test build #42704 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42704/consoleFull)
for PR 8790 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141599432
Yeah and actually I want to do one more verification to make sure the rest
of the history file is useful. Unfortunately my network connection is slow
that its a huge
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8799#discussion_r39913803
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/orc/OrcQuerySuite.scala ---
@@ -344,4 +344,34 @@ class OrcQuerySuite extends QueryTest with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8830#issuecomment-141606324
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user falaki commented on the pull request:
https://github.com/apache/spark/pull/8832#issuecomment-141606332
cc @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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8830#issuecomment-141606323
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/8505#issuecomment-141607040
Build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8505#issuecomment-141607033
Build triggered.
---
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/8823#issuecomment-141524234
Merged build started.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/8823#issuecomment-141524014
The fix is good. I only added comments. Will merge it to both master and
branch 1.5 once it passes jenkins.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8823#issuecomment-141524170
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8631#issuecomment-141533663
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/8631#issuecomment-141533658
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8806#discussion_r39889195
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/json/JacksonParser.scala
---
@@ -62,10 +62,23 @@ private[sql] object
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8825#issuecomment-141543900
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/8825#issuecomment-141543857
[Test build #42680 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42680/console)
for PR 8825 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8825#issuecomment-141543896
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/8826#issuecomment-141550686
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141593434
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/8828#issuecomment-141593432
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8828#issuecomment-141599896
ok it finally loaded. So the history UI for that task reports its still
RUNNING since it got the error parsing it. I guess that is ok. Ideally it
would still show
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8789#issuecomment-141602809
[Test build #42697 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42697/consoleFull)
for PR 8789 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8789#issuecomment-141603437
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/8830#issuecomment-141602715
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8830#issuecomment-141602769
Merged build started.
---
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/8830#issuecomment-141603326
[Test build #42706 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42706/consoleFull)
for PR 8830 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8789#issuecomment-141603434
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 Jianfeng-chs commented on a diff in the pull request:
https://github.com/apache/spark/pull/8801#discussion_r39914305
--- Diff: python/pyspark/sql/functions.py ---
@@ -189,6 +190,14 @@ def approxCountDistinct(col, rsd=None):
return Column(jc)
Github user falaki commented on the pull request:
https://github.com/apache/spark/pull/8832#issuecomment-141606839
Yes, if an application starts the JVM manually (not using spark-submit)
this call will fail. The change just adds safety without compromising
functionality or
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141596979
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/8790#issuecomment-141596949
**[Test build #42696 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42696/consoleFull)**
for PR 8790 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8790#issuecomment-141596978
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/8828#issuecomment-141597635
[Test build #42703 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42703/consoleFull)
for PR 8828 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8541#issuecomment-141598254
[Test build #42702 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42702/console)
for PR 8541 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8541#issuecomment-141598432
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/8541#issuecomment-141598434
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/8830#issuecomment-141606284
[Test build #42706 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42706/console)
for PR 8830 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8832#issuecomment-141606486
Any reason this would not be set ? My assumption was that all spark-submit
applications had this -- so I guess this is for applications not using
spark-submit ?
GitHub user zhichao-li opened a pull request:
https://github.com/apache/spark/pull/8811
[SPARK-10656][SQL]fix selection fails when a column has special characters
Best explained with this example:
val df = sqlContext.read.json(sqlContext.sparkContext.makeRDD(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8811#issuecomment-141369552
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8811#issuecomment-141369535
Merged build triggered.
---
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/8626#issuecomment-141378762
[Test build #42645 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42645/console)
for PR 8626 at commit
Github user navis commented on the pull request:
https://github.com/apache/spark/pull/8354#issuecomment-141379396
@JoshRosen It isn't because spark does not support "create macro". I've
tried to support that in new patch.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8354#issuecomment-141379468
Merged build triggered.
---
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 saucam commented on the pull request:
https://github.com/apache/spark/pull/8604#issuecomment-141396161
@yhuai thanks for the help!
---
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/8549#issuecomment-141411793
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-141411801
Merged build started.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141371746
This is based on https://github.com/apache/spark/pull/8089 by @JoshRosen
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141371791
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141371778
Merged build triggered.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8808#issuecomment-141371836
Thanks - I've merged 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 project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8639#issuecomment-141375112
[Test build #42646 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42646/console)
for PR 8639 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8639#issuecomment-141375249
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/8639#issuecomment-141375251
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/8813#issuecomment-141375199
[Test build #42650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42650/consoleFull)
for PR 8813 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/8735#issuecomment-141385993
I just found #8688 has been merged and looks it doesn't consider
backwards-compatibility.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-141387046
[Test build #42652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42652/consoleFull)
for PR 6767 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8804#issuecomment-141390717
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8804#issuecomment-141390624
Merged build triggered.
---
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/8812#issuecomment-141409104
[Test build #42649 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42649/console)
for PR 8812 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8812#issuecomment-141409154
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/8812#issuecomment-141409153
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/8809#issuecomment-141369191
[Test build #42641 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42641/console)
for PR 8809 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8354#issuecomment-141380026
[Test build #42651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42651/consoleFull)
for PR 8354 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-141385524
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6767#issuecomment-141385502
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8354#issuecomment-141408606
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/8354#issuecomment-141408568
[Test build #42651 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42651/console)
for PR 8354 at commit
1 - 100 of 615 matches
Mail list logo
