Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/281#issuecomment-39173387
Thanks, merged.
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39173844
Hey Xiangrui, why have a MLContext at all? Why not just make the input
methods part of MLUtils? This is the pattern we've followed with other input
methods (e.g.
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/245#discussion_r11148578
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -54,6 +54,12 @@ trait Vector extends Serializable {
* Converts the
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39174195
One other thing, for the centering, will we create a utility function for
it later? We should add a JIRA. I agree that they need to be removed by default.
---
If your
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39174557
@mengxr Ah... I totally understand your mean. Code is on the way.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-39175081
Hey @mateiz take another look ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/282
[SQL] SPARK-1372 Support for caching and uncaching tables in a SQLContext.
This doesn't yet support different databases in Hive (though you can
probably workaround this by calling `USE dbname`).
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/281
---
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/282#issuecomment-39175258
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/282#issuecomment-39175267
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 have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39176037
@mateiz Centering will be available after
https://github.com/apache/spark/pull/268 gets merged.
---
If your project is set up for it, you can reply to this email and have
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/245#discussion_r11149337
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -54,6 +54,12 @@ trait Vector extends Serializable {
* Converts the
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/245#issuecomment-39176607
@mateiz For `MLContext`, it used to be a context-like due to implicit
conversion. I'm a little bit afraid to see `MLUtils` becomes a collection of
random stuffs. To me,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/282#issuecomment-39178077
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/279#issuecomment-39178097
hey @pwendell so I am confused : did my commit actually go through :-)
I got a bunch of errors, and then it went through (atleast the script said
so !). Now I am
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/282#issuecomment-39178078
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13624/
---
If your project
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/283
SPARK-1380: Add sort-merge based cogroup/joins.
I've written cogroup/joins based on 'Sort-Merge' algorithm.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/284
SPARK-1338 scala style for explicitly specified types and short syntax f...
...or implicit evidence.
Wanted some early feedback. Build is supposed to fail.
You can merge this pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/284#issuecomment-39182574
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/284#issuecomment-39182557
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/283#issuecomment-39182558
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/283#issuecomment-39182575
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/284#issuecomment-39182697
Merged build finished.
---
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/284#issuecomment-39182698
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13625/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39185786
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39185768
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/195#issuecomment-39186014
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13627/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39186013
Merged build finished.
---
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/283#issuecomment-39187101
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/283#issuecomment-39187102
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13626/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/284#issuecomment-39191509
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/284#issuecomment-39191498
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/284#issuecomment-39191584
Merged build finished.
---
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/284#issuecomment-39191585
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13628/
---
If your project is set up for it, you can
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/284#discussion_r11154972
--- Diff:
project/spark-style/src/main/scala/org/apache/spark/scalastyle/SpaceAfterColonStyleCheck.scala
---
@@ -0,0 +1,39 @@
+/*
+ * Licensed to
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/284#discussion_r11155004
--- Diff:
project/spark-style/src/test/scala/org/apache/spark/scalastyle/CheckerTest.scala
---
@@ -0,0 +1,52 @@
+// Copyright (C) 2011-2012 the
Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/276#issuecomment-39199208
Thanks for the comments! The description of the GC effects was very
educational. I made the suggested changes. Let me know if you'd like to see
something else changed.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39201633
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39201623
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39203409
Hi, @mridulm I have modified code according to your suggestion, thank you!
Hi, @kayousterhout , I thought about your suggestion. I totally agree on
that the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39206333
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39206346
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 have this
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39206395
I haven't had a chance to look at this in detail yet, but I'm wondering if
this handles security at all?
I'm assuming the web UI still has the filters and acls I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39206558
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13630/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39206557
Build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39207086
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13629/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39207085
Merged build finished.
---
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/252#issuecomment-39208378
Hi @mateiz @mengxr , what do you think about the test? Besides, we could
also judge it from the hadoop-common code of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39208548
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/228#issuecomment-39208568
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 have
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11161910
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/rdd/VectorRDDFunctionsSuite.scala
---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the Apache Software
Github user kenahoo commented on the pull request:
https://github.com/apache/spark/pull/25#issuecomment-39213426
FWIW, I'm having the same problem both at `master`
(60abc252545ec7a5d59957a32e764cd18f6c16b4) and at `v0.9.0-incubating`. I am
not behind a proxy. I opened a ticket at
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39214799
Merged build finished.
---
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/228#issuecomment-39214800
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13631/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39215197
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39215180
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/275#issuecomment-39216306
Thank you @marmbrus , @rxin , both code and unittest whitelist have been
updated and passed the unit test in my local.
---
If your project is set up for it, you
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39217332
it's weird, in my mbp, all test cases are 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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/275#issuecomment-39218075
BTW, the whitelist has been reordered (via sort command of linux shell)
after adding more passed cases, and actually more cases would be added like
decimal_2 /
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39221975
Merged build finished.
---
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/195#issuecomment-39221977
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13632/
---
If your project is set up for it, you can
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/285
[SPARK-1371][WIP] Compression support for Spark SQL in-memory columnar
storage
JIRA issue: [SPARK-1373](https://issues.apache.org/jira/browse/SPARK-1373)
(Although tagged as WIP, this PR
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/216#discussion_r11167994
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/discretization/EntropyMinimizationDiscretizerSuite.scala
---
@@ -0,0 +1,71 @@
+/*
+ * Licensed
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/285#issuecomment-39226576
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 have
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/216#discussion_r11168845
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/discretization/EntropyMinimizationDiscretizer.scala
---
@@ -0,0 +1,317 @@
+/*
+ * Licensed to
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11169105
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11169142
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39229541
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39229530
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11169339
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11169437
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11169770
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/285#issuecomment-39232622
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11170791
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11170823
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39234699
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/228#issuecomment-39235976
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13634/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/228#issuecomment-39235975
Merged build finished.
---
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/284#discussion_r11172007
--- Diff:
project/spark-style/src/main/scala/org/apache/spark/scalastyle/SpaceAfterColonStyleCheck.scala
---
@@ -0,0 +1,39 @@
+/*
+ * Licensed to the
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39236711
Hey @tgravescs this will pick upon ACL's and filters if configured similar
to the other UI's. In terms of HDFS permission, this patch takes a simple
approach of having a
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/276#discussion_r11172504
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/impl/EdgePartition.scala ---
@@ -84,19 +87,13 @@ class EdgePartition[@specialized(Char, Int, Boolean,
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/276#issuecomment-39237641
Thanks @darabos. The change looks good to me other than the one place I
pointed out.
---
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/248#issuecomment-39239471
Merged build finished.
---
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 the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39239988
+1 !!! I have been asking for this multiple times on the mailing list and
finally see the light!!!
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240088
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240076
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/286#issuecomment-39240275
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13636/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240273
Merged build finished.
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240317
But will this work on YARN?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39239474
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13635/
---
If your project is set up for it, you can
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/286
Merge Hadoop Into Spark
This patch merges the Hadoop 0.20.2 source code into the Spark project.
I've thought about this a bunch and this will provide us with several benefits:
### More
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240734
The best way to have more lines than some project is to merge it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39242381
thanks @pwendell. I'm going to try to look at this more detail in the
next day or so.
The MapReduce history server would be one thing to compare to. It has
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39243472
I love hadoop-0.20.2 -- It is the best Hadoop I have ever used. Thanks
@pwendell for pulling this in.
---
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/248#issuecomment-39243756
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39243737
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/248#issuecomment-39244525
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13637/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39244523
Merged build finished.
---
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 commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39244805
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39244916
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 have
1 - 100 of 268 matches
Mail list logo
