Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7038#issuecomment-116832022
@thegiive have you verified that these are the only sources of mismatch?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116839202
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6870#issuecomment-116844989
I believe @davies implemented something similar before
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-116844877
[Test build #36039 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36039/consoleFull)
for PR 6648 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7025#issuecomment-116844897
[Test build #36035 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36035/console)
for PR 7025 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/5114#issuecomment-116844894
@jerryshao @ArcherShao any updates on this? @harishreedharan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/5392#discussion_r33514995
--- Diff:
core/src/main/scala/org/apache/spark/deploy/client/AppClient.scala ---
@@ -40,98 +37,139 @@ import org.apache.spark.util.{ActorLogReceive,
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6338
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116857979
[Test build #36016 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36016/console)
for PR 7004 at commit
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/5392#discussion_r33518043
--- Diff: core/src/main/scala/org/apache/spark/deploy/worker/Worker.scala
---
@@ -181,24 +190,31 @@ private[worker] class Worker(
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/5392#discussion_r33518507
--- Diff: core/src/main/scala/org/apache/spark/deploy/worker/Worker.scala
---
@@ -235,21 +250,47 @@ private[worker] class Worker(
* still not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116859295
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 squito commented on the pull request:
https://github.com/apache/spark/pull/6983#issuecomment-116862765
Hi @ckadner. I'm not the best person to review this, but just randomly saw
your comment. If you merge with master, and then push to your same branch, the
diff here on
Github user josepablocam commented on a diff in the pull request:
https://github.com/apache/spark/pull/6994#discussion_r33521980
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/stat/test/KSTest.scala ---
@@ -0,0 +1,191 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116866607
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 commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116867600
Looks like this is consistently failing SparkSubmitSuite:
```
[info] - includes jars passed in through --jars *** FAILED *** (1 minute)
```
I
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/7100
[SPARK-8715] ArrayOutOfBoundsException fixed for DataFrameStatSuite.crosstab
cc @yhuai
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6959#issuecomment-116872804
[Test build #36025 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36025/console)
for PR 6959 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116872961
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 marmbrus opened a pull request:
https://github.com/apache/spark/pull/7102
[HOTFIX] Fix whitespace style error
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark fixStyle
Alternatively you can review and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7094#issuecomment-116874420
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/7070#issuecomment-116875893
[Test build #36048 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36048/console)
for PR 7070 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7070#issuecomment-116875940
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6882#issuecomment-116814774
Thanks, merged to 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7095#issuecomment-116823278
[Test build #36023 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36023/console)
for PR 7095 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7091#issuecomment-116827645
Jenkins, this is ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7060
---
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/7077#issuecomment-116830955
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/6921#issuecomment-116830700
[Test build #36026 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36026/consoleFull)
for PR 6921 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116830742
[Test build #36014 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36014/consoleFull)
for PR 7077 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7096#issuecomment-116830856
@Rosstin can you update the pull request title to make it more descriptive?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user Rosstin opened a pull request:
https://github.com/apache/spark/pull/7098
Spark-8661: for LinearRegressionSuite.scala, changed javadoc-style comments
to regular multiline comments, to make copy-pasting R code more simple
for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7038#issuecomment-116834403
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/5805#issuecomment-116834414
[Test build #36031 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36031/consoleFull)
for PR 5805 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116837611
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/7025#issuecomment-116837713
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/7025#issuecomment-116837640
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/7093#issuecomment-116837989
Is there any way to exclude the example files from this rule? The examples
seems to require the ugly `//scalastyle:off` but println is totally okay in the
examples.
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4399#issuecomment-116845717
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/4399#issuecomment-116845685
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6981#discussion_r33514278
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetime.scala
---
@@ -0,0 +1,255 @@
+/*
+ * Licensed to the Apache
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6294#issuecomment-116847847
Yes, but @zsxwing does this affect the receiver management stuff you are
designing?
On Mon, Jun 29, 2015 at 2:07 PM, andrewor14 notificati...@github.com
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6920#issuecomment-116850715
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/7048#issuecomment-116852044
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/7048#issuecomment-116851867
[Test build #36029 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36029/console)
for PR 7048 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7096
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/7098#issuecomment-116856874
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6959#discussion_r33517504
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/util/UniqueObjectPool.java
---
@@ -0,0 +1,59 @@
+/*
+ * Licensed to the Apache
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/5392#discussion_r33519394
--- Diff: core/src/main/scala/org/apache/spark/deploy/worker/Worker.scala
---
@@ -510,13 +580,25 @@ private[worker] class Worker(
}
}
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/7092#issuecomment-116860641
I am merging it to branch 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6920
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6810#discussion_r33523518
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/AggregateSuite.scala ---
@@ -0,0 +1,59 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6648#issuecomment-116873695
[Test build #36039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36039/console)
for PR 6648 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6810#discussion_r33523492
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/AggregateSuite.scala ---
@@ -0,0 +1,59 @@
+/*
+ * Licensed to the Apache Software
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116873659
LGTM. Will merge it to master and branch 1.4 once jenkins passes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-116814823
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6981#issuecomment-116814808
@tarekauel Thanks for working on this. After a quick look on it, I'm think
most of these implementation are slow, which turn the Long the into
java.sql.Date, generate a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7095#issuecomment-116814828
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/7094#issuecomment-116814855
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7093#discussion_r33504113
--- Diff:
core/src/main/scala/org/apache/spark/network/nio/BlockMessage.scala ---
@@ -57,6 +57,7 @@ private[nio] class BlockMessage() {
}
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7093#discussion_r33504194
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -659,6 +660,7 @@ abstract class RDD[T: ClassTag](
* @param separateWorkingDir Use
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-116815035
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/7095#issuecomment-116815077
@mengxr Should we add wrapper around the `trees` methos in ensembles as
well? I'm not sure how we would manipulate java objects in python.
---
If your project is set
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116827354
I guess the real concern is over whether adding this dependency would
create JAR hell for our users. Maybe @vanzin or @srowen could comment on this?
---
If your
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116827359
Thanks. Merging in master branch-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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6606
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/7087#issuecomment-116832501
Could you also update the description to explain what you are doing here?
Because the description of PR will become the commit message when merging.
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7096#issuecomment-116832780
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6959#issuecomment-116832821
@JoshRosen Could you take a second pass? I should had addressed all the
previous comments.
---
If your project is set up for it, you can reply to this email and have
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7025#issuecomment-116835942
ok to test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116839496
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4399#issuecomment-116845210
ok to test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7025#issuecomment-116845091
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1767#issuecomment-116845178
Hi @maropu would you mind closing this PR? It's confusing to have both open.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7090#issuecomment-116846607
I'm going to merge this into master to unbreak the master SBT tests.
Thanks!
---
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/6750#issuecomment-116848880
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 AiHe commented on the pull request:
https://github.com/apache/spark/pull/6338#issuecomment-116855167
Thank you guys!
---
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 pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116858240
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/7099#issuecomment-116858383
[Test build #36036 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36036/console)
for PR 7099 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7094#issuecomment-116858402
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 and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116858494
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/7101#issuecomment-116874600
[Test build #36047 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36047/consoleFull)
for PR 7101 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6959#issuecomment-116874722
@JoshRosen Thanks, I'm merging this 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-116814938
[Test build #36022 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36022/consoleFull)
for PR 6973 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-116814934
[Test build #36012 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36012/console)
for PR 6921 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7095#issuecomment-116815810
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/7095#issuecomment-116815878
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7038#discussion_r33508453
--- Diff:
core/src/main/scala/org/apache/spark/deploy/master/WorkerInfo.scala ---
@@ -107,4 +107,8 @@ private[spark] class WorkerInfo(
def
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/7087#discussion_r33508451
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -131,20 +131,22 @@ trait HiveTypeCoercion {
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7038#issuecomment-116831567
OK TO TEST
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7038#issuecomment-116831720
I think we should have the JSON protocol do whatever the normal UI does.
This change looks fine.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6205#issuecomment-116835114
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 feynmanliang opened a pull request:
https://github.com/apache/spark/pull/7099
[SPARK-8539][SPARK-8539][ML] Linear Regression Training and Testing Results
Adds results (e.g. objective value at each iteration, residuals) on
training and user-specified test sets for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7097#issuecomment-116835092
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/7097#issuecomment-116835113
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/7098#issuecomment-116835082
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6205#issuecomment-116835136
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/5502#issuecomment-116839827
@mtimper please file a JIRA at https://issues.apache.org/jira/browse/SPARK
and reopen a new patch against the master branch. Would you mind closing this
patch?
---
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-116843845
@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 this feature
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6931#issuecomment-116844196
@navis looks like this is already fixed. Would you mind closing this patch?
---
If your project is set up for it, you can reply to this email and have your
reply
601 - 700 of 1332 matches
Mail list logo
