Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41837372
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9081#issuecomment-147639157
[Test build #43635 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43635/consoleFull)
for PR 9081 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9084#issuecomment-147642601
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/9089#issuecomment-147642587
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/9089#issuecomment-147642538
[Test build #43633 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43633/console)
for PR 9089 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9084#issuecomment-147642518
[Test build #43622 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43622/console)
for PR 9084 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9084#issuecomment-147642599
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/9089#issuecomment-147642585
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/9026#issuecomment-147644840
Makes sense. Is it a problem that we actually have two metastores? Maybe
not. That's my only question, looking at this from the outside.
---
If your project is set up
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8976#issuecomment-147645261
Yeah you'll still have to filter this spurious binary compatibility check
warning:
```
[error] * method
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9050#issuecomment-147624248
[Test build #43621 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43621/console)
for PR 9050 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9050#issuecomment-147624308
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/8453#issuecomment-147624407
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/9050#issuecomment-147624305
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8916#issuecomment-147625179
LGTM, cc @liancheng to take another look.
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9091#discussion_r41833362
--- Diff: core/src/main/scala/org/apache/spark/rpc/RpcAddress.scala ---
@@ -0,0 +1,50 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9091#issuecomment-147626977
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/9050#issuecomment-147630724
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 ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147636061
@rxin Thanks, I added the Experimental tags.
---
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 ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/9089#discussion_r41836429
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -362,14 +362,35 @@ class Analyzer(
j
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9078#issuecomment-147642051
[Test build #43637 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43637/consoleFull)
for PR 9078 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9078#issuecomment-147641313
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/8453#issuecomment-147651856
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/8453#issuecomment-147651853
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 zhichao-li opened a pull request:
https://github.com/apache/spark/pull/9096
[Core]Remove useless if branch
We don't need the if checking here. it's redundant. The final result would
always use `hstr`
You can merge this pull request into a Git repository by running:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8945#issuecomment-147626144
[Test build #43628 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43628/consoleFull)
for PR 8945 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147627183
We can tag them as Experimental (even though the entire DataFrame API is
experimental!)
---
If your project is set up for it, you can reply to this email and have your
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9089#discussion_r41833942
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -362,14 +362,35 @@ class Analyzer(
j
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147637636
[Test build #43633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43633/consoleFull)
for PR 9089 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9093#issuecomment-147641225
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/9093#issuecomment-147641224
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/9093#issuecomment-147641155
[Test build #43632 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43632/console)
for PR 9093 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9078#issuecomment-147640719
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/9089#issuecomment-147643826
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/9089#issuecomment-147643952
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/9081#issuecomment-147647068
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/9081#issuecomment-147647067
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/9095#issuecomment-147649000
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 jerryshao opened a pull request:
https://github.com/apache/spark/pull/9095
[SPARK-11082][YARN] Fix wrong core number when response vcore is less than
requested vcore
This should be guarded out and use response vcore number, this will be
happened when use
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9095#issuecomment-147649014
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/9095#issuecomment-147656903
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/9096#issuecomment-147656764
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/9095#issuecomment-147656497
[Test build #43639 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43639/console)
for PR 9095 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9096#issuecomment-147656720
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/9095#issuecomment-147656906
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user KaiXinXiaoLei closed the pull request at:
https://github.com/apache/spark/pull/8947
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8453#issuecomment-147624706
[Test build #43627 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43627/consoleFull)
for PR 8453 at commit
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147625512
@marmbrus I addressed your comments from the review about a month ago:
1. Foreign key references now store the referenced relation directly as a
logical plan
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9078#issuecomment-147628251
[Test build #43626 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43626/console)
for PR 9078 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9078#issuecomment-147628290
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/9078#issuecomment-147628289
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/9092#issuecomment-147628224
[Test build #43630 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43630/consoleFull)
for PR 9092 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/9094
[SPARK-11036][SQL] AttributeReference should not be assigned new expression
id inside tasks
JIRA: https://issues.apache.org/jira/browse/SPARK-11036
Related to #9093, SPARK-11036 is proposed
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9092#issuecomment-147640440
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/9092#issuecomment-147640443
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147642886
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/9086#issuecomment-147624010
cc @rxin @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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9092#issuecomment-147627765
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/9092#issuecomment-147627734
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9038#issuecomment-147631386
See #9093 for an exploration of some sketchy-looking `newExprId` calls
which might be involved in the problems that we're experiencing here.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9050#issuecomment-147639405
[Test build #1887 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1887/consoleFull)
for PR 9050 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9092#issuecomment-147639962
[Test build #43630 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43630/console)
for PR 9092 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147646844
[Test build #43638 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43638/consoleFull)
for PR 9089 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9081#issuecomment-147647003
[Test build #43635 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43635/console)
for PR 9081 at commit
Github user jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41839587
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9085#issuecomment-147654556
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/9090#issuecomment-147623285
[Test build #43623 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43623/consoleFull)
for PR 9090 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-147622583
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/9050#issuecomment-147623169
[Test build #43624 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43624/consoleFull)
for PR 9050 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9085#issuecomment-147624909
[Test build #43625 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43625/consoleFull)
for PR 9085 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9084#discussion_r41833851
--- Diff: core/src/main/scala/org/apache/spark/memory/MemoryManager.scala
---
@@ -72,46 +92,62 @@ private[spark] abstract class MemoryManager {
def
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9093#issuecomment-147631990
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/9093#issuecomment-147631968
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/9089#issuecomment-147634492
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/9085#issuecomment-147634471
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/9085#issuecomment-147634491
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/9089#issuecomment-147634467
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/9091#issuecomment-147634406
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 jbonofre commented on a diff in the pull request:
https://github.com/apache/spark/pull/9059#discussion_r41837043
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/AllJobsPage.scala ---
@@ -289,13 +290,15 @@ private[ui] class AllJobsPage(parent: JobsTab)
extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9094#issuecomment-147641277
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/9078#issuecomment-147641283
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/9094#issuecomment-147641314
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/8453#issuecomment-147651548
[Test build #43627 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43627/console)
for PR 8453 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9095#issuecomment-147651353
[Test build #43639 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43639/consoleFull)
for PR 9095 at commit
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/9090
[SPARK-7402][ML] JSON SerDe for standard param types
This PR implements the JSON SerDe for the following param types: `Boolean`,
`Int`, `Long`, `Float`, `Double`, `String`, `Array[Int]`,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9050#issuecomment-147620479
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9090#discussion_r41831432
--- Diff: mllib/src/main/scala/org/apache/spark/ml/param/params.scala ---
@@ -287,6 +422,16 @@ class StringArrayParam(parent: Params, name: String,
doc:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9050#issuecomment-147620505
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/9090#issuecomment-147620477
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/9090#issuecomment-147620504
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8916#issuecomment-147623900
Thank you @cloud-fan for the reviewing, updated, and passed the unit test.
---
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/9091#issuecomment-147626999
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/9090#issuecomment-147628837
[Test build #43623 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43623/console)
for PR 9090 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9090#issuecomment-147628990
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/9090#issuecomment-147628985
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 JoshRosen opened a pull request:
https://github.com/apache/spark/pull/9093
[SPARK-11080] Throw exception when NamedExpression.newExprId is called
inside tasks
My understanding of `NamedExpression.newExprId` is that it is only intended
to be called on the driver. If it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9085#issuecomment-147638012
[Test build #43634 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43634/consoleFull)
for PR 9085 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9094#issuecomment-147642286
[Test build #43636 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43636/consoleFull)
for PR 9094 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9085#issuecomment-147654388
[Test build #43625 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43625/console)
for PR 9085 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9085#issuecomment-147654560
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
101 - 200 of 763 matches
Mail list logo
