Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-196814809
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-196814782
**[Test build #53195 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53195/consoleFull)**
for PR 11730 at commit
[`b520eb5`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-196814798
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-196814299
**[Test build #53195 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53195/consoleFull)**
for PR 11730 at commit
[`b520eb5`](https://gi
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/11730
[SPARK-13894][SQL] SqlContext.range return type from DataFrame to DataSet
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-13894
Change
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196798704
**[Test build #53191 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53191/consoleFull)**
for PR 11725 at commit
[`c37dfed`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196799243
**[Test build #53194 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53194/consoleFull)**
for PR 11724 at commit
[`c144797`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196799066
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 projec
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/11209#discussion_r56154746
--- Diff:
sql/catalyst/src/test/java/org/apache/spark/sql/catalyst/expressions/XXH64Suite.java
---
@@ -0,0 +1,159 @@
+/*
+ * Licensed to the Apache So
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196799071
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196797771
**[Test build #53193 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53193/consoleFull)**
for PR 11725 at commit
[`d7c8cc6`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11729#issuecomment-196796397
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 p
GitHub user mbaddar1 opened a pull request:
https://github.com/apache/spark/pull/11729
[SPARK-13073] [MLib] [WIP] creating R like summary for logistic Regression
in Spark - Scala
## What changes were proposed in this pull request?
Implemented initial version of toString met
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196793416
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196793418
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196793149
**[Test build #53189 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53189/consoleFull)**
for PR 11717 at commit
[`06bc187`](https://g
Github user trueyao commented on a diff in the pull request:
https://github.com/apache/spark/pull/11719#discussion_r56152374
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -543,21 +543,22 @@ private[spark] class TaskSetManager(
cas
Github user breakdawn commented on the pull request:
https://github.com/apache/spark/pull/11727#issuecomment-196791813
That's fine, maybe next time.
---
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 breakdawn closed the pull request at:
https://github.com/apache/spark/pull/11727
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196791029
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196791033
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196790668
**[Test build #53187 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53187/consoleFull)**
for PR 11724 at commit
[`ed1d499`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196788731
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196788738
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11727#issuecomment-196788327
Yeah sorry we had a bit of a race condition here. I submitted the PR just
before this, and actually didn't realize there was a whole separate JIRA for
this one issue.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196787722
**[Test build #53182 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53182/consoleFull)**
for PR 11658 at commit
[`8de6365`](https://g
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11728#issuecomment-196787581
@zsxwing do you have an opinion?
I was thinking the max would be applied just to `availableProcessors()`,
but, yeah maybe a good idea to not even let the user set it
Github user breakdawn commented on the pull request:
https://github.com/apache/spark/pull/11727#issuecomment-196787205
I agree that the third annotation can be removed, the reason is the base
class DStream has marked it as transient anyway.
By the way, should i close this PR since
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11719#discussion_r56150936
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -543,21 +543,22 @@ private[spark] class TaskSetManager(
case
Github user trueyao commented on the pull request:
https://github.com/apache/spark/pull/11719#issuecomment-196783948
I'm really sorry to make extra commits...Are these codes clearer ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196780604
**[Test build #53192 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53192/consoleFull)**
for PR 11722 at commit
[`2e4eca4`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11721#issuecomment-196780449
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11721#issuecomment-196780452
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196780220
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 fe
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11721#issuecomment-196780179
**[Test build #53183 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53183/consoleFull)**
for PR 11721 at commit
[`6339a01`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11728#issuecomment-196769290
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 p
GitHub user yonran opened a pull request:
https://github.com/apache/spark/pull/11728
[SPARK-13906] Ensure that there are at least 2 dispatcher threads.
## What changes were proposed in this pull request?
Force at least two dispatcher-event-loop threads. Since
SparkDeploySch
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-196767388
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-196767390
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-196767151
**[Test build #53181 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53181/consoleFull)**
for PR 11720 at commit
[`f8b7910`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11726#issuecomment-196764461
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11726#issuecomment-196764456
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11726#issuecomment-196764252
**[Test build #53190 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53190/consoleFull)**
for PR 11726 at commit
[`150c79a`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10242#issuecomment-196761978
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10242#issuecomment-196761979
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10242#issuecomment-196761704
**[Test build #53188 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53188/consoleFull)**
for PR 10242 at commit
[`4ab456c`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11727#issuecomment-196758568
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 p
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196760369
**[Test build #53185 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53185/consoleFull)**
for PR 11722 at commit
[`2e4eca4`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196760430
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196760428
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 projec
Github user Fokko commented on a diff in the pull request:
https://github.com/apache/spark/pull/10839#discussion_r56143177
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/linalg/distributed/BlockMatrix.scala
---
@@ -268,8 +268,26 @@ class BlockMatrix @Since("1.3.0") (
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11727#issuecomment-196758277
This is covered by https://github.com/apache/spark/pull/11725 I agree with
the changes, except that I think that in the third instance the annotation
actually won't mak
GitHub user breakdawn opened a pull request:
https://github.com/apache/spark/pull/11727
[SPARK-13397] Cleanup transient annotations which aren't being applied
## What changes were proposed in this pull request?
This cleanup the transient annotations which aren't being applie
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196757482
**[Test build #53191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53191/consoleFull)**
for PR 11725 at commit
[`c37dfed`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11726#issuecomment-196757378
**[Test build #53190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53190/consoleFull)**
for PR 11726 at commit
[`150c79a`](https://gi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11692#issuecomment-196756805
@vanzin @jerryshao does that sound right?
---
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 projec
GitHub user sun-rui opened a pull request:
https://github.com/apache/spark/pull/11726
[SPARK-13905][SPARKR] Change implementation of as.data.frame() to avoid
conflict with the ones in the R base package.
## What changes were proposed in this pull request?
SparkR provides a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196754591
**[Test build #53189 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53189/consoleFull)**
for PR 11717 at commit
[`06bc187`](https://gi
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196754674
This PR would allow to infer `TimestampType` more flexibly (e.g. includeing
`T` and `GMT`) rather than just using `Timestamp.valueOf()`.
---
If your project is se
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11702#issuecomment-196754018
Merged to master back to 1.4
---
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 hav
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10242#issuecomment-196753549
**[Test build #53188 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53188/consoleFull)**
for PR 10242 at commit
[`4ab456c`](https://gi
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11702
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196752898
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196752896
**[Test build #53186 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53186/consoleFull)**
for PR 11725 at commit
[`6b28bea`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196752899
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11702#issuecomment-196752770
I'm going to go ahead and merge. It passes, and clearly this change was
already intended to be in the source.
---
If your project is set up for it, you can reply to thi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196751935
**[Test build #53187 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53187/consoleFull)**
for PR 11724 at commit
[`ed1d499`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196751981
**[Test build #53186 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53186/consoleFull)**
for PR 11725 at commit
[`6b28bea`](https://gi
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196751413
There should be a conflict with https://github.com/apache/spark/pull/11550.
I will resolve the conflict as soon as either this one or that one is
merged.
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/11725
[SPARK-13823] [CORE] More warnings, StandardCharset follow up
## What changes were proposed in this pull request?
Follow up to https://github.com/apache/spark/pull/11657
- Also upda
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196749567
cc @rxin @falaki
---
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/11724
[SPARK-13866][SQL] Handle decimal type in CSV inference at CSV data source.
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-13866
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196746553
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196746554
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196746337
**[Test build #53180 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53180/consoleFull)**
for PR 11717 at commit
[`798eceb`](https://g
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/10607#issuecomment-196746310
@sethah merged to master. Ping me when the remaining work on
[SPARK-12326](https://issues.apache.org/jira/browse/SPARK-12326) is ready for
review.
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196746027
**[Test build #53185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53185/consoleFull)**
for PR 11722 at commit
[`2e4eca4`](https://gi
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10607
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11719#discussion_r56137442
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -557,7 +557,7 @@ private[spark] class TaskSetManager(
lastLa
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196743792
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196743793
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196743467
**[Test build #53179 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53179/consoleFull)**
for PR 11717 at commit
[`11dcc3d`](https://g
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/10355#discussion_r56136601
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/DecisionTreeClassifierSuite.scala
---
@@ -334,6 +334,51 @@ class DecisionTreeClassifierSuit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-196743359
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 p
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-196743025
@BenFradet I'm ok with doing the other things like evaluators in a
different PR - however the only concern I'd have is it would temporarily break
things like `CrossValid
GitHub user hbhanawat opened a pull request:
https://github.com/apache/spark/pull/11723
[SPARK-13904][Scheduler]Add support for pluggable cluster manager
## What changes were proposed in this pull request?
This commit adds support for pluggable cluster manager. And also all
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-196742174
Surething
---
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
e
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11628#issuecomment-196741708
Here's an alternate take in light of comments above, to illustrate what I'm
thinking of:
```
...
val proc = pb.start()
val env = SparkEnv.g
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-196741326
@BenFradet if it's not too much trouble, I think you can do
`AFTSurvivalRegression` and `IsotonicRegression` here.
---
If your project is set up for it, you can reply t
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196739239
**[Test build #53184 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53184/consoleFull)**
for PR 11722 at commit
[`fb6c8cd`](https://gi
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/11722
[SPARK-13903][SQL] Modify output nullability with constraints for Join
operator
## What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-13903
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11628#discussion_r56134160
--- Diff: core/src/main/scala/org/apache/spark/rdd/PipedRDD.scala ---
@@ -176,6 +197,8 @@ private[spark] class PipedRDD[T: ClassTag](
fals
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11628#discussion_r56133901
--- Diff: core/src/main/scala/org/apache/spark/rdd/PipedRDD.scala ---
@@ -176,6 +197,8 @@ private[spark] class PipedRDD[T: ClassTag](
fals
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11628#discussion_r56133820
--- Diff: core/src/test/scala/org/apache/spark/rdd/PipedRDDSuite.scala ---
@@ -50,6 +50,29 @@ class PipedRDDSuite extends SparkFunSuite with
SharedSparkContex
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733804
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733060
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196733132
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733812
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196733125
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733050
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 projec
701 - 800 of 890 matches
Mail list logo
