Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148357955
[Test build #43785 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43785/consoleFull)
for PR 6841 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9135#issuecomment-148377755
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 philipphoffmann opened a pull request:
https://github.com/apache/spark/pull/9135
[SPARK-11129][MESOS] Link Spark WebUI from Mesos WebUI
Mesos has a feature for linking to frameworks running on top of Mesos
from the Mesos WebUI. This commit enables Spark to make use
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9110#issuecomment-148345206
[Test build #1905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1905/consoleFull)
for PR 9110 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148353456
[Test build #43783 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43783/console)
for PR 9134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148353596
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/6841#issuecomment-148354870
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/6841#issuecomment-148354846
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9126#issuecomment-148361565
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148371225
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/8416#issuecomment-148343732
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/8416#issuecomment-148343731
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9061#issuecomment-148343787
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148350047
[Test build #43784 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43784/console)
for PR 6841 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148350051
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/6841#issuecomment-148350050
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 zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148356438
Check the test report. Seems the failed unit tests are unrelated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148356952
@srowen Agree. I prefer to narrow the change of this PR, too. Reverted my
previous commit.
---
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/9116#issuecomment-148359930
[Test build #43786 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43786/consoleFull)
for PR 9116 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148360061
I think it's OK, but what does it help? if warnings are to be treated as
errors, they are errors like others. Does it become confusing to log an error
that says "warn"?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148371226
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/9110#issuecomment-148374359
[Test build #1905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1905/console)
for PR 9110 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148342506
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/9123#issuecomment-148342359
[Test build #43778 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43778/console)
for PR 9123 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148342508
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148345442
Hm, this is getting unwieldy. There are several nested try blocks here. The
same argument goes for many of these methods -- if one fails should they not
continue trying?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148349307
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/6841#issuecomment-148349331
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/9134#issuecomment-148353599
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/9116#issuecomment-148358652
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/9116#issuecomment-148358633
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9134#discussion_r42111793
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -655,6 +655,15 @@ object SparkSubmit {
// scalastyle:on println
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6841#discussion_r42108278
--- Diff: project/SparkBuild.scala ---
@@ -33,13 +33,17 @@ object BuildCommons {
private val buildLocation =
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148349695
**[Test build #43770 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43770/console)**
for PR 9131 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148371080
[Test build #43786 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43786/console)
for PR 9116 at commit
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/9134#discussion_r42121597
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -655,6 +655,15 @@ object SparkSubmit {
// scalastyle:on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148343576
[Test build #43780 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43780/console)
for PR 8416 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9110#issuecomment-148344776
OK thank you, I probably should have suspected it was on purpose. Seems OK
to me.
---
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/9131#issuecomment-148349751
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/9131#issuecomment-148349750
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/6841#issuecomment-148349753
[Test build #43784 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43784/consoleFull)
for PR 6841 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9129#issuecomment-148292467
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/9129#issuecomment-148292403
[Test build #43766 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43766/console)
for PR 9129 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9129#issuecomment-148292465
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/9131#issuecomment-148294627
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/9131#issuecomment-148294652
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/9132#issuecomment-148294626
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/9132#issuecomment-148294651
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/9131#issuecomment-148296105
[Test build #43770 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43770/consoleFull)
for PR 9131 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9132#issuecomment-148296156
[Test build #43769 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43769/consoleFull)
for PR 9132 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9123#discussion_r42089770
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -135,4 +135,21 @@ class AnalysisSuite extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148305056
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/8652#issuecomment-148305081
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/8652#issuecomment-148310064
[Test build #43775 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43775/console)
for PR 8652 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148310086
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 dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/9123#discussion_r42092689
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/AnalysisSuite.scala
---
@@ -135,4 +135,21 @@ class AnalysisSuite extends
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/9123#discussion_r42092649
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -482,7 +482,12 @@ class Analyzer(
val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148310087
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/9123#issuecomment-148314896
[Test build #43778 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43778/consoleFull)
for PR 9123 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3677#issuecomment-148319006
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/3677#issuecomment-148319023
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/9134#issuecomment-148323656
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/9132#issuecomment-148323716
[Test build #43773 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43773/console)
for PR 9132 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148323628
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9132#issuecomment-148298153
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9132#issuecomment-148298043
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/9134#issuecomment-148302621
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/9134#issuecomment-148302613
[Test build #43774 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43774/console)
for PR 9134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148302625
Test FAILed.
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/8362#issuecomment-148306575
we can create a hash expression, and codegen that. And then just use
hyperloglog(hash(field)).
---
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/9123#issuecomment-148306706
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/9123#issuecomment-148306682
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9116#discussion_r42092604
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/StreamingContext.scala ---
@@ -694,31 +694,39 @@ class StreamingContext private[streaming] (
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148315435
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/8652#issuecomment-148315405
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/9132#issuecomment-148323855
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/8923#issuecomment-148298768
[Test build #43772 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43772/consoleFull)
for PR 8923 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148314571
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/8416#issuecomment-148316257
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/8416#issuecomment-148316285
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/9130#issuecomment-148317713
[Test build #43767 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43767/console)
for PR 9130 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9130#issuecomment-148317795
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/9130#issuecomment-148317796
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/9096#issuecomment-148325206
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/9096#issuecomment-148325204
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/3677#issuecomment-148333298
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/3677#issuecomment-148333299
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/9123#issuecomment-148335260
[Test build #43776 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43776/console)
for PR 9123 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148335402
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/9123#issuecomment-148335401
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9131
[SPARK-9][SQL] cleanup for unsafe array and map
The purpose of this PR is to keep the unsafe format detail only inside the
unsafe class itself, so when we use them(like use unsafe array in
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-148297180
cc @pwendell @kayousterhout thoughts on this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148300028
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/9134#issuecomment-148300064
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/9134#issuecomment-148301968
[Test build #43774 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43774/consoleFull)
for PR 9134 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148305296
@yhuai, after some investigation, I think the we still can optimize the
left/right/full outer join in broadcasting way if they don't have condition,
but LeftSemi
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9123#discussion_r42091740
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -482,7 +482,12 @@ class Analyzer(
val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148307180
[Test build #43776 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43776/consoleFull)
for PR 9123 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148310218
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/9116#issuecomment-148310203
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
1 - 100 of 603 matches
Mail list logo
