Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40790470
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14230/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40790467
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40790471
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14231/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40790466
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40790469
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14229/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40790468
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/443#issuecomment-40790451
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14228/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/446#issuecomment-40790412
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 proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/443#issuecomment-40790450
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 have
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/446
[Spark-1461] Deferred Expression Evaluation (short-circuit evaluation)
Short-circut will significantly improves the performance in Expression
Evaluation, however, we can not fold an determinis
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/445#issuecomment-40789732
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 proj
GitHub user whenceforth opened a pull request:
https://github.com/apache/spark/pull/445
SPARK-1532 Provide option in ec2/spark_ec2.py to set more restrictive
Source in the security groups.
SPARK-1532 add option to ec2/spark_ec2.py to permit more restrictive IP
address to EC2 instan
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/442#issuecomment-40788640
+1 BTW I submitted a fix for this in jblas, although it is not yet released.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788558
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/444#issuecomment-40788548
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 ha
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788428
Yes, agree with you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fe
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788426
ok pushed
---
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 a
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788376
Actually never mind I will do it here. You can't just change that line
without changing the indent anyway.
---
If your project is set up for it, you can reply to this email
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788363
Sure. I'll modify 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 f
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788337
Can you submit a PR for that?
---
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 th
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40788273
@pwendell I really want to disable Jenkins for this PR but I didn't find
how to do it.
---
If your project is set up for it, you can reply to this email and have your
repl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40788256
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40788261
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 the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40788214
Yep, I think python shell's document should be update same time.
sys.version_info only became a named tuple in 2.7. To get this to work in 2.6,
it needs to be accessed as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40787436
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40787444
I did but haven't had time to figure out why the tests are failing (the
tests don't run properly on my laptop). Hoping this was a Jenkins issue and
the re-launched
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/443#issuecomment-40787433
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/444#issuecomment-40787435
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/443#issuecomment-40787424
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40787425
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/444#issuecomment-40787422
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 ha
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/444
Fixed broken pyspark shell.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark pyspark
Alternatively you can review and apply these changes
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/443
README update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark readme
Alternatively you can review and apply these changes as the patch a
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40787330
Jenkins, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40787295
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40787296
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14227/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40787253
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40787245
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 this
Github user tmyklebu commented on the pull request:
https://github.com/apache/spark/pull/442#issuecomment-40787028
This appears to be a PySpark error unrelated to my change.
---
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/442#issuecomment-40786793
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/441#issuecomment-40786798
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14225/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/441#issuecomment-40786792
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/300#issuecomment-40786800
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14223/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/442#issuecomment-40786797
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14226/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/300#issuecomment-40786795
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40786799
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14224/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40786794
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 have
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/299#discussion_r11763430
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -123,6 +142,14 @@ object SparkSubmit {
val options = List[OptionA
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/442#issuecomment-40785546
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/442#issuecomment-40785554
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 tmyklebu opened a pull request:
https://github.com/apache/spark/pull/442
ALS: Avoid the garbage-creating ctor of DoubleMatrix
`new DoubleMatrix(double[])` creates a garbage `double[]` of the same
length as its argument and immediately throws it away. This pull request
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/432#issuecomment-40785366
Actually I was not able to merge. Somehow I can't write to the asf repo ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user berngp commented on the pull request:
https://github.com/apache/spark/pull/433#issuecomment-40785313
@andrewor14 thanks for the review and feedback!
---
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 proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/441#issuecomment-40785283
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/441#issuecomment-40785286
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/432#issuecomment-40785265
ok i 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 this feature
e
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/441
[Fix #204] Eliminate delay between binding and log checking
In the existing history server, the user needs to wait
`spark.history.updateInterval` seconds before his/her logs show up on the UI.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40785124
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/438#issuecomment-40785121
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40785115
Jenkins, 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
Github user berngp commented on a diff in the pull request:
https://github.com/apache/spark/pull/433#discussion_r11763222
--- Diff:
yarn/common/src/test/scala/org/apache/spark/deploy/yarn/ClientBaseSpec.scala ---
@@ -0,0 +1,97 @@
+/*
+ * Licensed to the Apache Software Foun
Github user berngp commented on a diff in the pull request:
https://github.com/apache/spark/pull/433#discussion_r11763107
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -378,55 +378,48 @@ object ClientBase {
val APP_JAR: String = "a
Github user berngp commented on a diff in the pull request:
https://github.com/apache/spark/pull/433#discussion_r11763070
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -378,55 +378,48 @@ object ClientBase {
val APP_JAR: String = "a
Github user berngp commented on a diff in the pull request:
https://github.com/apache/spark/pull/433#discussion_r11763060
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -378,55 +378,48 @@ object ClientBase {
val APP_JAR: String = "a
Github user berngp commented on a diff in the pull request:
https://github.com/apache/spark/pull/433#discussion_r11763040
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -378,55 +378,48 @@ object ClientBase {
val APP_JAR: String = "a
Github user berngp commented on a diff in the pull request:
https://github.com/apache/spark/pull/433#discussion_r11763026
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -378,55 +378,48 @@ object ClientBase {
val APP_JAR: String = "a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/300#issuecomment-40784017
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/300#issuecomment-40784012
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 ha
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/354#issuecomment-40782397
@marmbrus do we need to add these new methods to the Python API too now? It
sounds like you just need to forward through to the methods.
---
If your project is set up for
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/383#issuecomment-40782324
@kayousterhout not sure if you saw my comment, this looks good but the
exception message is somewhat confusing. It would be good to update that.
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40781680
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. If your p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40781681
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14222/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780535
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780530
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 this
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780446
Yes, we should do it. It looks pretty good.
---
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
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780447
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 this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/440
---
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 enabl
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/432#issuecomment-40779916
This looks good to me. @pwendell please merge.
On Apr 17, 2014 6:24 PM, "UCB AMPLab" wrote:
> All automated tests passed.
> Refer to this link for build
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/375#issuecomment-40779766
@vanzin I recently experienced what you mean on a YARN cluster myself. I've
looked at your patch and I think it's a good fix for Spark on YARN. Could you
submit a PR fo
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/375#issuecomment-40779781
On a separate note, @pwendell this PR is ready for merge.
---
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/440#issuecomment-40779608
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14218/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40779607
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14221/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/432#issuecomment-40779603
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/440#issuecomment-40779605
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40779604
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/432#issuecomment-40779606
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14219/
---
If your project
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/440#issuecomment-40779213
I wonder if we should also disable the first three tests of
https://github.com/apache/spark/blob/master/core/src/test/scala/org/apache/spark/ui/UISuite.scala.
They are
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40777909
I had to kill this build because it was hung up and blocking some other
builds. It was hung up by a separate test issue unrelated to this patch...
sorry, we can re-run it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40777902
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40777903
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14220/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40777878
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/439#issuecomment-40777871
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40777873
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/30#issuecomment-40777872
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/30#issuecomment-40777875
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14216/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40777876
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14215/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/439#issuecomment-40777874
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14217/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/438#issuecomment-40777430
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/439
---
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 enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/422#issuecomment-40777424
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 ha
1 - 100 of 218 matches
Mail list logo
