Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2862#issuecomment-59869372
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21948/consoleFull)
for PR 2862 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59869757
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21955/consoleFull)
for PR 2520 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2746#issuecomment-59869868
I think the main objection @pwendell and I have against the policy is not
that it is complicated in terms of implementation, but that it is complicated
in terms of
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2696#discussion_r19126684
--- Diff:
core/src/main/scala/org/apache/spark/ui/jobs/JobProgressListener.scala ---
@@ -40,17 +40,25 @@ class JobProgressListener(conf: SparkConf) extends
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/2732#issuecomment-59870049
Could you also take a look at #2748, backport for branch 1.1?
---
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/2746#issuecomment-59870868
With regard to the configuration barrier, I actually think the exposed
configs are pretty straightforward. I think even the inexperienced user can
reason about the
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2696#discussion_r19127119
--- Diff:
core/src/main/scala/org/apache/spark/ui/jobs/JobProgressListener.scala ---
@@ -40,17 +40,25 @@ class JobProgressListener(conf: SparkConf)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2866#issuecomment-59871327
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/2866#issuecomment-59871323
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21951/consoleFull)
for PR 2866 at commit
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59871504
Jenkins, please start the test!
---
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/2839#issuecomment-59871491
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21949/consoleFull)
for PR 2839 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2839#issuecomment-59871497
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/2869#issuecomment-59871644
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21954/consoleFull)
for PR 2869 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2696#issuecomment-59871647
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21956/consoleFull)
for PR 2696 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2869#issuecomment-59871646
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/2866#issuecomment-59871966
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21957/consoleFull)
for PR 2866 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2864#issuecomment-59871965
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21958/consoleFull)
for PR 2864 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2867#issuecomment-59872492
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/2867#issuecomment-59872487
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21952/consoleFull)
for PR 2867 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2867#issuecomment-59872654
@kayousterhout This might integrate nicely with my #2852, which introduces
some new abstractions to simplify the web UI's table rendering code. With my
framework, I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2864#issuecomment-59875799
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21958/consoleFull)
for PR 2864 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2864#issuecomment-59875800
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/2696#issuecomment-59875884
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21956/consoleFull)
for PR 2696 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2696#issuecomment-59875888
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/2866#issuecomment-59876264
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21957/consoleFull)
for PR 2866 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2866#issuecomment-59876271
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/2743#issuecomment-59876269
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/409/consoleFull)
for PR 2743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59876465
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/409/consoleFull)
for PR 2743 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59876974
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/2520#issuecomment-59876973
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21955/consoleFull)**
for PR 2520 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59877524
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59877519
Jenkins, add to whitelist.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59877728
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59877740
@davies this should have been fixed, not sure what is going on.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59877748
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21959/consoleFull)
for PR 2868 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59877812
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/2868#issuecomment-59877810
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21959/consoleFull)
for PR 2868 at commit
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/2870
[SPARK-4023] [MLlib] [PySpark] convert rdd into RDD of Vector
Convert the input rdd to RDD of Vector.
cc @mengxr
You can merge this pull request into a Git repository by running:
$ git
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59877987
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59878023
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21960/consoleFull)
for PR 2743 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59878121
@pwendell There are two PullRequestBuilder plugins, one is work, another
one (called NewSparkPullRequestBuilder) is still failing.
---
If your project is set up for it,
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59878151
@davies ah I see, thanks. This should have triggered the old one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59878293
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21962/consoleFull)
for PR 2520 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2870#issuecomment-59878295
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21961/consoleFull)
for PR 2870 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59878761
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 codedeft commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59878898
Seems like lots of line too long messages. Will address this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59879138
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21963/consoleFull)
for PR 2520 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2866#issuecomment-59879420
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2866#issuecomment-59879396
;retest
---
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 scwf commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-59879567
We can reproduce the golden answer for hive 0.13 as i done in my closed PR,
how about that?
---
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/2866#issuecomment-59879704
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21964/consoleFull)
for PR 2866 at commit
Github user codedeft commented on the pull request:
https://github.com/apache/spark/pull/2868#issuecomment-59879666
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/2868#issuecomment-59879975
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21965/consoleFull)
for PR 2868 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-59880136
@scwf, which PR?
---
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/2868#issuecomment-59880277
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21966/consoleFull)
for PR 2868 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129869
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129854
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129863
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129850
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129866
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129859
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129853
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129857
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19129865
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-59880350
@scwf The golden answer is different in hive12 and hive13. We need some
extra shim layer to handle that.
---
If your project is set up for it, you can reply to this
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-59880636
@marmbrus I think he refers to https://github.com/apache/spark/pull/2499
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2701#issuecomment-59881165
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21967/consoleFull)
for PR 2701 at commit
Github user zhzhan commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-59881210
@scwf Did you also replace the query plan for hive0.13 in your another PR?
because I also saw some query plan changes in hive0.13.
---
If your project is set up for it,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2850#issuecomment-59881463
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21968/consoleFull)
for PR 2850 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-59881474
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/2520#issuecomment-59881469
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21962/consoleFull)
for PR 2520 at commit
GitHub user shivaram opened a pull request:
https://github.com/apache/spark/pull/2871
[WIP] [SPARK-4031] Make torrent broadcast read blocks on use.
This avoids reading broadcast variables when they are referenced in the
closure but not used by the code.
Note: This is a WIP and
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2871#issuecomment-59881787
This seems likely to merge-conflict with my PR #2844, so I'd like to merge
that one first.
---
If your project is set up for it, you can reply to this email and have
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/2871#issuecomment-59881872
@JoshRosen -- yes, that should be fine. I will rebase once #2844 is checked
in
---
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/2743#issuecomment-59882034
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/2866#issuecomment-59882025
Oh wow. 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59882030
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21960/consoleFull)
for PR 2743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2087#issuecomment-59882086
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21971/consoleFull)
for PR 2087 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2871#issuecomment-59882084
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21970/consoleFull)
for PR 2871 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2866#issuecomment-59882089
Actually instead of introducing a new one, what if we introduce a
compressed bitmap that tracks zero-sized blocks, and then use avg size to track
only non-zero blocks?
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2870#issuecomment-59882352
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21961/consoleFull)
for PR 2870 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2870#issuecomment-59882356
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/2087#issuecomment-59882564
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
301 - 383 of 383 matches
Mail list logo
