Github user colorant commented on the pull request:
https://github.com/apache/spark/pull/2031#issuecomment-52737048
the config value is case irrelevant , if you notice that there is a
toLowerCase transform later ;)
---
If your project is set up for it, you can reply to this email
Github user hzw19900416 closed the pull request at:
https://github.com/apache/spark/pull/2050
---
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
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1958#issuecomment-52737388
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1958#issuecomment-52737616
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18927/consoleFull)
for PR 1958 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52737850
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18925/consoleFull)
for PR 1545 at commit
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/2052
fix SparkContextSchedulerCreationSuite test error
run test with the master branch with this command
sbt/sbt -Pyarn -Phadoop-2.3 -Dhadoop.version=2.3.0 -Pkinesis-as
-Phive-thriftserver test-only
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2052#issuecomment-52740144
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 jerryshao opened a pull request:
https://github.com/apache/spark/pull/2053
[SPARK-3146][Streaming] Improve the flexibility of Spark Streaming Kafka API
Improve the flexibility of Spark Streaming Kafka API to offer user the
ability to pre-process message before stored
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1958#issuecomment-52740385
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18927/consoleFull)
for PR 1958 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52740586
**Tests timed out** after a configured wait of `120m`.
---
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/2053#issuecomment-52740578
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18928/consoleFull)
for PR 2053 at commit
Github user CrazyJvm commented on the pull request:
https://github.com/apache/spark/pull/2031#issuecomment-52741370
@colorant thanks, I've not noticed `toLowerCase ` before : ) . already
modified
---
If your project is set up for it, you can reply to this email and have your
reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52741946
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52742343
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18933/consoleFull)
for PR 1545 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52742350
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18933/consoleFull)
for PR 1545 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52742473
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52742587
Hi everyone, thanks for your comments. I have tested the latest commit and
I think this is ready to go in my opinion. I have fixed the PySpark behavior
where the
Github user isaias commented on the pull request:
https://github.com/apache/spark/pull/2048#issuecomment-52742677
@rxin, the trait ActorLogReceive gets the concrete implementation through
receiveWithLogging function overriding of implementing Actor and applying it,
so I think that
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52742757
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18934/consoleFull)
for PR 1845 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52742759
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18936/consoleFull)
for PR 1545 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52742752
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18936/consoleFull)
for PR 1545 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52742770
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18934/consoleFull)
for PR 1845 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2048#issuecomment-52742926
You just need to change
```scala
override def isDefinedAt(o: Any): Boolean =
_receiveWithLogging.isDefinedAt(o)
```
to
```scala
override
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52743041
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52743537
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18937/consoleFull)
for PR 1845 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52743530
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18937/consoleFull)
for PR 1845 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52743675
Hm, 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52743953
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18938/consoleFull)
for PR 1845 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52743943
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18938/consoleFull)
for PR 1845 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52744147
Jenkins is failing because of some mllib / streaming leftover state
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52744175
Let me try this once more. 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.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1845#issuecomment-52744341
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18939/consoleFull)
for PR 1845 at commit
Github user isaias commented on the pull request:
https://github.com/apache/spark/pull/2048#issuecomment-52744357
@rxin Very nice, it works. Should be better to close this PR and send
another just with the trait changes?
BR
---
If your project is set up for it, you can
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2048#issuecomment-52745114
Sure.
---
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 isaias closed the pull request at:
https://github.com/apache/spark/pull/2048
---
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 isaias commented on the pull request:
https://github.com/apache/spark/pull/2048#issuecomment-52745159
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 have this feature
enabled
Github user mubarak commented on a diff in the pull request:
https://github.com/apache/spark/pull/1723#discussion_r16463252
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/DStream.scala ---
@@ -106,6 +106,27 @@ abstract class DStream[T: ClassTag] (
/**
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2054#issuecomment-52746053
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18942/consoleFull)
for PR 2054 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52746058
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18943/consoleFull)
for PR 1723 at commit
Github user mubarak commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52746109
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2054#discussion_r16463419
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ByteArrayChunkOutputStream.scala
---
@@ -0,0 +1,82 @@
+/*
+ * Licensed to the Apache Software
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/2053#issuecomment-52746388
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
GitHub user isaias opened a pull request:
https://github.com/apache/spark/pull/2055
[SPARK-2312] Logging Unhandled messages
The previous solution has changed based on
https://github.com/apache/spark/pull/2048 discussions.
You can merge this pull request into a Git repository by
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-52748199
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18946/consoleFull)
for PR 2035 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2053#issuecomment-52748195
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18945/consoleFull)
for PR 2053 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-52748211
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18946/consoleFull)
for PR 2035 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2055#issuecomment-52748507
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1931#discussion_r16464399
--- Diff: core/src/main/scala/org/apache/spark/ContextCleaner.scala ---
@@ -66,10 +66,15 @@ private[spark] class ContextCleaner(sc: SparkContext)
extends
Github user chutium commented on the pull request:
https://github.com/apache/spark/pull/2044#issuecomment-52748630
actually i totally agree with you @liancheng , this was reported in user
list
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2036#issuecomment-52748646
The unit test failure probably due to the assembly jar with duplicated
netty jars (netty.3.2.2.Final.jar netty.3.6.6.Final.jar, the class
`NioWorker` with
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/2053#issuecomment-52749189
Hey @tdas , mind taking a look at this? Looks like checkpoint file messed
up the environment.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-52750288
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18943/consoleFull)
for PR 1723 at commit
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2056
[SPARK-3139] Akka timeouts from ContextCleaner when cleaning shuffles
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-3139
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2054#issuecomment-52751016
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18942/consoleFull)
for PR 2054 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52751321
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18947/consoleFull)
for PR 2056 at commit
Github user isaias commented on the pull request:
https://github.com/apache/spark/pull/2055#issuecomment-52752384
After send the PR I realized that I could have written some tests based on
underlyingActor and isDefinedAt, if is valuable I can do it.
BR
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52752829
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18948/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52753280
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18949/consoleFull)
for PR 2056 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2057#issuecomment-52755341
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 scwf opened a pull request:
https://github.com/apache/spark/pull/2057
SPARK_LOGFILE and SPARK_ROOT_LOGGER no longer need in spark-daemon.sh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scwf/spark patch-7
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/1964#issuecomment-52756284
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/1964#issuecomment-52756243
Hi @erikerlandson,
Thank you for your comment.
I modify the code according to your advice.
Would you please check it.
- DistanceMeasure trait
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2046#discussion_r16468398
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/TestSuiteBase.scala ---
@@ -119,7 +119,12 @@ trait TestSuiteBase extends FunSuite with
Github user baishuo commented on the pull request:
https://github.com/apache/spark/pull/1919#issuecomment-52758525
Here I try to explain my design idea(the code is mostly in
InsertIntoHiveTable.scala) :
lets assume there is a table called table1,which has 2 columns:col1,col2,
and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52759438
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18949/consoleFull)
for PR 2056 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1958
---
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 bbossy commented on the pull request:
https://github.com/apache/spark/pull/2014#issuecomment-52769500
Yes, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52769948
QA tests have started for PR 1905. This patch DID NOT merge cleanly!
brView progress:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52772733
QA tests have started for PR 1905. This patch DID NOT merge cleanly!
brView progress:
GitHub user YanTangZhai opened a pull request:
https://github.com/apache/spark/pull/2058
Update global variables of HttpBroadcast so that multiple SparkContexts can
coexist
Update global variables of HttpBroadcast so that multiple SparkContexts can
coexist
You can merge this pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52775792
QA results for PR 2058:br- This patch FAILED unit tests.brbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52775780
QA tests have started for PR 2058. This patch DID NOT merge cleanly!
brView progress:
Github user roji commented on the pull request:
https://github.com/apache/spark/pull/1875#issuecomment-52777250
@mateiz, added a commit for the sbin scripts.
In general the scripts could use a bit of cleanup - the bin and sbin
scripts work a bit differently, the sbin-specific
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1875#issuecomment-52777692
QA tests have started for PR 1875. This patch DID NOT merge cleanly!
brView progress:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1875#issuecomment-5203
QA results for PR 1875:br- This patch FAILED unit tests.brbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52780307
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18954/consoleFull)
for PR 2058 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52780297
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18954/consoleFull)
for PR 2058 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52781729
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18955/consoleFull)
for PR 2058 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52781827
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18955/consoleFull)
for PR 2058 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52783094
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18956/consoleFull)
for PR 2056 at commit
GitHub user YanTangZhai opened a pull request:
https://github.com/apache/spark/pull/2059
[SPARK-3148] Update global variables of HttpBroadcast so that multiple
SparkContexts can coexist
Update global variables of HttpBroadcast so that multiple SparkContexts can
coexist
You can
Github user YanTangZhai commented on the pull request:
https://github.com/apache/spark/pull/2058#issuecomment-52783462
#2059
---
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 YanTangZhai closed the pull request at:
https://github.com/apache/spark/pull/2058
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52783748
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18957/consoleFull)
for PR 2056 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52783769
QA tests have started for PR 1905. This patch DID NOT merge cleanly!
brView progress:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52783790
QA results for PR 1905:br- This patch FAILED unit tests.brbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2059#issuecomment-52783775
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18958/consoleFull)
for PR 2059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2059#issuecomment-52783760
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18958/consoleFull)
for PR 2059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52784460
QA results for PR 1905:br- This patch FAILED unit tests.brbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52784438
QA tests have started for PR 1905. This patch DID NOT merge cleanly!
brView progress:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2059#issuecomment-52785971
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18961/consoleFull)
for PR 2059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2059#issuecomment-52785960
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18961/consoleFull)
for PR 2059 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52787468
QA tests have started for PR 1905. This patch DID NOT merge cleanly!
brView progress:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1905#issuecomment-52788067
QA results for PR 1905:br- This patch FAILED unit tests.brbrFor more
information see test
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/1958#issuecomment-52791480
@tdas @harishreedharan This is causing yarn builds to fail on branch-1.1.
I think you are missing commit:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-52791960
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18957/consoleFull)
for PR 2056 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52806013
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52806728
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18963/consoleFull)
for PR 1545 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52806071
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/2030#issuecomment-52807817
@aarondav The table and graph in
https://github.com/apache/spark/pull/2030#issuecomment-52693339 compares pre-PR
to post-PR. Actually it breaks it down into three runs:
1 - 100 of 409 matches
Mail list logo
