Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14953
**[Test build #64912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64912/consoleFull)**
for PR 14953 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/14953
[Minor] [ML] [MLlib] Remove work around for breeze sparse matrix.
## What changes were proposed in this pull request?
Since we have updated breeze version to 0.12, we should remove work
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/14452#discussion_r77446696
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/subquery/CommonSubquery.scala
---
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14859
**[Test build #64911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64911/consoleFull)**
for PR 14859 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14859
**[Test build #64910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64910/consoleFull)**
for PR 14859 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14919
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64909/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14919
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14919
**[Test build #64909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64909/consoleFull)**
for PR 14919 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14928
Can you update the pull request title / description to say more about the
actual issue?
---
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 issue:
https://github.com/apache/spark/pull/14919
**[Test build #64909 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64909/consoleFull)**
for PR 14919 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/13690
@vectorijk Is this ready for another round of review ?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14433
---
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 shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/14433#discussion_r77443065
--- Diff: core/src/main/scala/org/apache/spark/internal/Logging.scala ---
@@ -135,7 +135,8 @@ private[spark] trait Logging {
val replLevel =
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14433
Merged into master
---
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,
Github user wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/14945#discussion_r77442963
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamTest.scala ---
@@ -152,8 +152,8 @@ trait StreamTest extends QueryTest with
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/14952#discussion_r77442140
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -520,10 +520,11 @@ private[spark] class BlockManager(
*
*
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14952
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64908/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14952
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14952
**[Test build #64908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64908/consoleFull)**
for PR 14952 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14881
---
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 issue:
https://github.com/apache/spark/pull/14951
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14951
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64907/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14951
**[Test build #64907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64907/consoleFull)**
for PR 14951 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14915#discussion_r77441612
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/TreeNode.scala
---
@@ -604,6 +604,7 @@ abstract class TreeNode[BaseType <:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14828
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64906/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14828
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14828
**[Test build #64906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64906/consoleFull)**
for PR 14828 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14948
Ah yeah, it also removes runs from k-means||. The good news is I think
these changes are actually not overlapping for the most part, and where they
do, they're essentially the same change.
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/14948
I think https://github.com/apache/spark/pull/14937 also removes runs. cc
@yanboliang can we coordinate these PRs?
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14952
**[Test build #64908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64908/consoleFull)**
for PR 14952 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14952
/cc @ericl
---
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
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/14952
[SPARK-17110] Fix StreamCorruptionException in
BlockManager.getRemoteValues()
## What changes were proposed in this pull request?
This patch fixes a `java.io.StreamCorruptedException`
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/1
that was basically the idea behind the trait you requested me to remove...
the thing is I don't feel it belongs to CreateNamedStruct, so I settled for
putting it in CreateStruct and reusing it in
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14950
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14950
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64905/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14950
**[Test build #64905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64905/consoleFull)**
for PR 14950 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14951
cc @cloud-fan @hvanhovell @davies @sameeragarwal
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14951
**[Test build #64907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64907/consoleFull)**
for PR 14951 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/14951
[SPARK-17391] [TEST] Fix Two Test Failures After Backport
### What changes were proposed in this pull request?
In the latest branch 2.0, we have two test case failure due to backport.
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14550
I need to fix the test case failure in Branch 2.0
---
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 issue:
https://github.com/apache/spark/pull/14864
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64901/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14864
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14864
**[Test build #64901 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64901/consoleFull)**
for PR 14864 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14797
This does not catch all the cases. In CTAS, we still optimize the query. By
following the way in this PR, I can try to fix that case. Thanks!
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14949
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14949
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64903/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14949
**[Test build #64903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64903/consoleFull)**
for PR 14949 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14938
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14938
Merging to master/branch-2.0.
---
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14867#discussion_r77439638
--- Diff:
sql/catalyst/src/main/antlr4/org/apache/spark/sql/catalyst/parser/SqlBase.g4 ---
@@ -374,15 +374,17 @@ setQuantifier
;
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14828
**[Test build #64906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64906/consoleFull)**
for PR 14828 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/1
Why not share the method for creating the named children, and use that in
CreateUnsafeStruct?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/1
thanks, I think I came up with something simpler, I've implemented the
logic in CreateStruct and reused it for CreateStructUnsafe by calling
CreateStruct(children), then extracting the new children
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/1
Something like this:
```scala
object CreateNamedStruct {
def nameColumns(expressions: Seq[Expression]): Seq[Expression] = {
expressions.zipWithIndex.flatMap {
case
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14950
**[Test build #64905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64905/consoleFull)**
for PR 14950 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/14950
@srowen not only cpu cost, if data dimension is big, serialization cost
will be big, such as https://github.com/apache/spark/pull/14109
and compute all target seems not proper if we may add
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14950
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14950
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64904/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14950
**[Test build #64904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64904/consoleFull)**
for PR 14950 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14950
**[Test build #64904 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64904/consoleFull)**
for PR 14950 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14950
Hm how much does this really save? these are pretty cheap sufficient
statistics. Now you have to know whether your particular object was configured
or not to return the answer you want.
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14950
**[Test build #64902 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64902/consoleFull)**
for PR 14950 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14950
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14950
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64902/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14949
**[Test build #64903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64903/consoleFull)**
for PR 14949 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14864#discussion_r77438939
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/DataSourceScanExec.scala
---
@@ -156,24 +155,57 @@ case class FileSourceScanExec(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14950
**[Test build #64902 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64902/consoleFull)**
for PR 14950 at commit
GitHub user WeichenXu123 opened a pull request:
https://github.com/apache/spark/pull/14950
[SPARK-17390][ML][MLLib] Optimize MultivariantOnlineSummerizer by making
the summarized target configurable
## What changes were proposed in this pull request?
add a mask parameter
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/1
Can you suggest an other approach to prevent duplication of the code that
constructs the 'named' arguments?
On Sep 3, 2016 19:16, "Herman van Hovell" wrote:
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14302
backported to 2.0
---
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,
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/1
@eyalfa there are IMO still two more things to do:
1. Get rid of the `CreateStructLikeFactory`; that is way to complicated for
what you are trying to do.
2. Touch up the tests in
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/14864#discussion_r77438866
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/DataSourceScanExec.scala
---
@@ -156,24 +156,57 @@ case class FileSourceScanExec(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14864
**[Test build #64901 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64901/consoleFull)**
for PR 14864 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14550
backported to 2.0
---
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,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14944
Yeah, I also hit it.
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14946
It sounds like all the build 2.0 failed the same test case.
https://amplab.cs.berkeley.edu/jenkins/job/spark-branch-2.0-test-sbt-hadoop-2.3/
Let me try to fix it.
---
If
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14864#discussion_r77438506
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/DataSourceScanExec.scala
---
@@ -156,24 +156,57 @@ case class FileSourceScanExec(
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14550
yea, go ahead :)
---
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,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14949
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14949
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64900/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14949
**[Test build #64900 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64900/consoleFull)**
for PR 14949 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14864
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14864
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64898/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14948
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14948
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64899/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14864
**[Test build #64898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64898/consoleFull)**
for PR 14864 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14948
**[Test build #64899 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64899/consoleFull)**
for PR 14948 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13767
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/13767
Merged to master/2.0 as that was obviously the intent of the test cleanup
logic
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14949
**[Test build #64900 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64900/consoleFull)**
for PR 14949 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14577
I think we should not make this particular change and can close this PR.
It's possible another similar change could be OK.
---
If your project is set up for it, you can reply to this email and have
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/14949
[SPARK-17057] [ML] ProbabilisticClassifierModels' prediction more
reasonable with multi zero thresholds
## What changes were proposed in this pull request?
See related discussion at
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14948
**[Test build #64899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64899/consoleFull)**
for PR 14948 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14948
Note this also now resolves SPARK-3261. This change already means that with
k-means|| init, fewer than k cluster centers may be returned, which is probably
correct (and faster). Now random init will
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14864
**[Test build #64898 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64898/consoleFull)**
for PR 14864 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/14864
@cloud-fan : Thanks !! Did the change.
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13767
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64897/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13767
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13767
**[Test build #64897 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64897/consoleFull)**
for PR 13767 at commit
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/1
@cloud-fan , @hvanhovell , can you please review this? it's been waiting
for some time now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
1 - 100 of 151 matches
Mail list logo