Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9073#discussion_r42272109
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/clustering/KMeansSuite.scala ---
@@ -104,5 +104,6 @@ class KMeansSuite extends SparkFunSuite with
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/7417#discussion_r42272013
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -274,12 +275,30 @@ private[sql] abstract class
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9073#discussion_r42272083
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -24,6 +24,7 @@ import org.apache.spark.ml.util.{Identifiable,
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9073#discussion_r42272087
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -117,6 +118,14 @@ class KMeansModel private[ml] (
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8652#discussion_r42272078
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQuerySuite.scala
---
@@ -69,6 +71,58 @@ class HiveQuerySuite extends
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9144#issuecomment-148789432
@vanzin
---
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/9135#issuecomment-148789532
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/9130#issuecomment-148790775
Thanks - I've merged this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9144#issuecomment-148797797
[Test build #43843 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43843/consoleFull)
for PR 9144 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148798108
Are we certain that we only get `NoClassDefFoundError` but not also
`ClassNotFoundException`? I wonder if we should just check for either of those
in the match. Also
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148798288
Actually, this one has not been merged yet (weird thing happened while
merging it), @koertkuipers please go ahead to address the comment.
---
If your project is set up
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8652#discussion_r42272209
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HivePlanTest.scala
---
@@ -17,6 +17,7 @@
package
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9073#issuecomment-148788033
That should be it---thanks!
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9144#issuecomment-148790293
LGTM. 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
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8866#issuecomment-148793612
Thanks for your updates! Let me know if the proposal sounds workable.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/8866#discussion_r42274055
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/DecisionTreeRegressor.scala
---
@@ -39,7 +40,7 @@ import org.apache.spark.sql.DataFrame
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9075#issuecomment-148796371
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9145#discussion_r42278053
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/GenerateColumnAccessor.scala
---
@@ -0,0 +1,149 @@
+/*
+ * Licensed to the Apache
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/8884#issuecomment-148769776
@Lewuathe
They should be the same, but there is no test proving it.
Since in
```scala
test("linear regression with weighted samples"){
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9138#issuecomment-148784377
/cc @andrewor14 @zsxwing I think you're the people most familiar with this
code.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user NarineK commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148787306
Hi @felixcheung,
thanks for your comments.
1. I'm a bit confused - why create a seq of indices? instead can't we use
lapply on allColNames?
yes, that's
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9069#issuecomment-148788943
[Test build #1916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1916/consoleFull)
for PR 9069 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9149#issuecomment-148789247
@lababidi please file a JIRA and add it to the title of the PR. See how
other PRs are opened.
---
If your project is set up for it, you can reply to this email and
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8652#discussion_r42272725
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQuerySuite.scala
---
@@ -69,6 +71,58 @@ class HiveQuerySuite extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9144#issuecomment-148791764
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/9144#issuecomment-148791740
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9132#issuecomment-148783875
LGTM, would be good to backport into 1.5.
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9069#issuecomment-148788590
@bhargav Thanks for the update! LGTM pending tests
---
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 pull request:
https://github.com/apache/spark/pull/9075#issuecomment-148795961
[Test build #43840 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43840/console)
for PR 9075 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9069#issuecomment-148796105
[Test build #1916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1916/console)
for PR 9069 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9075#issuecomment-148796367
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9044#issuecomment-148805746
I'll take another look at [https://github.com/apache/spark/pull/8609] now.
Can you please close this duplicate PR?
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148805581
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/9122#discussion_r42277272
--- Diff: python/pyspark/context.py ---
@@ -280,6 +280,18 @@ def __exit__(self, type, value, trace):
"""
self.stop()
+
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9145#discussion_r42277995
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/GenerateColumnAccessor.scala
---
@@ -0,0 +1,149 @@
+/*
+ * Licensed to the Apache
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-148809195
(incidentally, I just realized this info is totally missing from the json,
filed https://issues.apache.org/jira/browse/SPARK-11155)
---
If your project is set up for
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9056#issuecomment-148809251
@yhuai @liancheng
---
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9109#discussion_r42264562
--- Diff: docs/_plugins/include_example.rb ---
@@ -0,0 +1,70 @@
+require 'octopress-code-highlighter'
+require 'liquid'
+
+module Octopress
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9109#discussion_r42264578
--- Diff: docs/index.md ---
@@ -12,6 +12,8 @@ It also supports a rich set of higher-level tools
including [Spark SQL](sql-prog
# Downloading
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9109#discussion_r42264565
--- Diff: docs/_plugins/include_example.rb ---
@@ -0,0 +1,70 @@
+require 'octopress-code-highlighter'
+require 'liquid'
+
+module Octopress
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9109#discussion_r42264567
--- Diff: docs/_plugins/include_example.rb ---
@@ -0,0 +1,70 @@
+require 'octopress-code-highlighter'
+require 'liquid'
+
+module Octopress
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9109#discussion_r42264560
--- Diff: docs/_config.yml ---
@@ -2,6 +2,7 @@ highlighter: pygments
markdown: kramdown
gems:
- jekyll-redirect-from
+ -
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9089#issuecomment-148786929
@ankurdave Np, thanks for the fix. Btw, should the fix be accompanied by
a unit test to catch that issue?
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9135#issuecomment-148792599
[Test build #43842 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43842/consoleFull)
for PR 9135 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/8866#discussion_r42273886
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/param/shared/SharedParamsCodeGen.scala
---
@@ -44,6 +44,8 @@ private[shared] object SharedParamsCodeGen
GitHub user damnMeddlingKid opened a pull request:
https://github.com/apache/spark/pull/9151
Packserv
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Shopify/spark packserv
Alternatively you can review and apply these changes
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9059#issuecomment-148807086
[Test build #43845 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43845/consoleFull)
for PR 9059 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9132#discussion_r42269957
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SQLListener.scala ---
@@ -126,7 +126,13 @@ private[sql] class SQLListener(conf:
Github user ryan-williams commented on a diff in the pull request:
https://github.com/apache/spark/pull/9147#discussion_r42271853
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala ---
@@ -62,10 +62,23 @@ private[spark] class ApplicationMaster(
Github user NarineK commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148787814
Hi @felixcheung,
thanks for your comments.
1. I'm a bit confused - why create a seq of indices? instead can't we use
lapply on allColNames?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9147#issuecomment-148790093
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/9135#issuecomment-148790133
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/9135#issuecomment-148790098
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/9147#issuecomment-148790122
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/9129#issuecomment-148792900
@KaiXinXiaoLei can you close this PR? Also next time please open an
accompanying JIRA and add it to the title of your PR.
---
If your project is set up for it, you
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9145#discussion_r42275706
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/ColumnType.scala ---
@@ -28,6 +28,36 @@ import org.apache.spark.sql.types._
import
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/9096#discussion_r42275658
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskLocation.scala
---
@@ -64,10 +64,10 @@ private[spark] object TaskLocation {
*/
Github user damnMeddlingKid closed the pull request at:
https://github.com/apache/spark/pull/9151
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9145#issuecomment-148804511
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 SherlockYang opened a pull request:
https://github.com/apache/spark/pull/9150
[Spark-10994] Add local clustering coefficient computation in GraphX
The local clustering coefficient of a vertex (node) in a graph quantifies
how close its neighbours are to being a clique
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9150#issuecomment-148770205
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9069#issuecomment-148794016
Btw, it doesn't matter what you call your branch name; that's not a problem.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/8416#discussion_r42274201
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -123,6 +124,24 @@ class DataFrameReader private[sql](sqlContext:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9147#issuecomment-148793946
[Test build #43841 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43841/consoleFull)
for PR 9147 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9151#issuecomment-148799659
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9145#discussion_r42275556
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeFormatter.scala
---
@@ -44,11 +45,13 @@ private class CodeFormatter
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9145#issuecomment-148804541
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/9096#issuecomment-148804209
@zhichao-li This looks fine, but are there other implications? In
`TaskSetManager` there are entire blocks of code that are not executed before
this patch.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-148805580
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/9059#issuecomment-148805547
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/8829#issuecomment-148805552
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9145#discussion_r42278194
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/InMemoryColumnarTableScan.scala
---
@@ -43,7 +42,7 @@ private[sql] object InMemoryRelation {
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/8984#discussion_r42263878
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1880,4 +1880,46 @@ setMethod("as.data.frame",
stop(paste("Unused argument(s): ", paste(list(...),
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-148775462
Much better. :-) 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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9075#issuecomment-148778827
Tested this patch in a 5 nodes cluster. Each node has an executor, the
executor core is 1 and the receiver number is 5.
Before this patch, there were several
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9026#issuecomment-148782895
ah, btw, can you fix the pr description to reflect the actual change?
thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9151#issuecomment-148799331
@damnMeddlingKid can you close this PR 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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9145#discussion_r42277711
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/GenerateColumnAccessor.scala
---
@@ -0,0 +1,149 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-148806897
[Test build #43846 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43846/consoleFull)
for PR 8829 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9145#issuecomment-148806821
[Test build #43844 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43844/consoleFull)
for PR 9145 at commit
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-148808343
Also jumping in late, but I agree with @andrewor14 , I think we should just
change duration to (1), that would be the most useful. My vote is for (last
task end) -
Github user avulanov commented on the pull request:
https://github.com/apache/spark/pull/8757#issuecomment-148817255
@jkbradley According to the time taken it actually did the shuffle.
However, I am not sure how useful in practice these block-diagonal matrices.
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9147#issuecomment-148822901
[Test build #43848 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43848/consoleFull)
for PR 9147 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7950#issuecomment-148824693
Hey @davies @angelini, what's the status / final verdict on this PR? Should
we still consider bumping Pyrolite for 1.6?
---
If your project is set up for it, you can
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8652#discussion_r42286218
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -268,6 +268,27 @@ private[sql] abstract class SparkStrategies
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/8101#discussion_r42286254
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/jdbc/PostgresIntegrationSuite.scala
---
@@ -0,0 +1,75 @@
+/*
+ * Licensed to the Apache
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5368#issuecomment-148825149
Hey @tigerquoll, would you mind closing this PR for now? It sounds like
this is going to need some more work or discussion, so I think we should close
this until it's
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8652#discussion_r42286246
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -268,6 +268,27 @@ private[sql] abstract class SparkStrategies
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9120#issuecomment-148825207
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/9120#issuecomment-148825286
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6291#issuecomment-148827020
Hey @markhamstra, what's the status of this PR? Do you have time to address
Kay's latest comment? It's been open for a while and I'd like to get it merged
soon if you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9135#issuecomment-148839422
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148839614
LGTM, left one minor comment.
---
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/9135#issuecomment-148839421
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8323#issuecomment-148840605
@gliptak I had an offline discussion with @davies . Let's do the following:
1. Change L259 in `pyspark/tests.py` to:
~~~python
# Regression
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8615#issuecomment-148842506
@kevincox, by no means is this rejecting the idea of upgrading to 0.9; I
was only suggesting that we close this PR and re-open once it's ready for
further review. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9147#issuecomment-148842465
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/9147#issuecomment-148842488
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/7401#issuecomment-148842500
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9069
---
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
1 - 100 of 633 matches
Mail list logo
