Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2483#discussion_r17955115
--- Diff:
external/kafka/src/test/scala/org/apache/spark/streaming/kafka/KafkaStreamSuite.scala
---
@@ -59,16 +58,35 @@ class KafkaStreamSuite extends
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2464#issuecomment-56628837
@mubarak Thank you very much for this fix! Its finally merged!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/2515
[SPARK-3675][SQL] Allow starting a JDBC server on an existing context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2515#issuecomment-56629604
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20744/consoleFull)
for PR 2515 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2514#issuecomment-56629824
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20742/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2514#issuecomment-56629822
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20742/consoleFull)
for PR 2514 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2483#issuecomment-56632476
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20743/consoleFull)
for PR 2483 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2483#issuecomment-56632481
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20743/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2515#issuecomment-56633081
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20744/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2515#issuecomment-56633079
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20744/consoleFull)
for PR 2515 at commit
GitHub user tigerquoll opened a pull request:
https://github.com/apache/spark/pull/2516
Spark Core - [SPARK-3620] - Refactor of SparkSubmit Argument parsing code
Argument processing seems to have gotten a lot of attention lately, so I
thought I might throw my contribution into the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2516#issuecomment-56634577
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 project
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/2435#discussion_r17957565
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/RandomForest.scala ---
@@ -0,0 +1,430 @@
+/*
+ * Licensed to the Apache Software
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/2435#discussion_r17957573
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/RandomForest.scala ---
@@ -0,0 +1,430 @@
+/*
+ * Licensed to the Apache Software
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2514#discussion_r17957564
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/ExternalSorter.scala ---
@@ -152,7 +152,7 @@ private[spark] class ExternalSorter[K, V, C](
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/2435#discussion_r17957577
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/impl/DTStatsAggregator.scala
---
@@ -189,6 +160,230 @@ private[tree] class DTStatsAggregator(
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/2435#discussion_r17957595
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/impl/DTStatsAggregator.scala
---
@@ -189,6 +160,230 @@ private[tree] class DTStatsAggregator(
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/2435#discussion_r17957666
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/impl/DTStatsAggregator.scala
---
@@ -189,6 +160,230 @@ private[tree] class DTStatsAggregator(
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/2517
[SPARK-3676][Sql]spark sql hive test suite failed in JDK 1.6
https://issues.apache.org/jira/browse/SPARK-3676
spark sql hive test failed in jdk 1.6, you can replay this by set jdk
version =
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2517#issuecomment-56636736
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 project
GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/2518
SPARK-3663 Document SPARK_LOG_DIR and SPARK_PID_DIR
These descriptions are from the header of spark-daemon.sh
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2518#issuecomment-56638326
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20745/consoleFull)
for PR 2518 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2517#issuecomment-56639208
actually this is a bug in jdk6
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4428022
---
If your project is set up for it, you can reply to this email and have
Github user Ishiihara commented on a diff in the pull request:
https://github.com/apache/spark/pull/2490#discussion_r17959346
--- Diff: docs/programming-guide.md ---
@@ -1121,6 +1121,11 @@ than shipping a copy of it with tasks. They can be
used, for example, to give ev
large
Github user Ishiihara commented on a diff in the pull request:
https://github.com/apache/spark/pull/2490#discussion_r17959656
--- Diff: docs/programming-guide.md ---
@@ -1183,6 +1188,10 @@ running on the cluster can then add to it using the
`add` method or the `+=` ope
GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/2519
SPARK-3526 Add section about data locality to the tuning guide
cc @kayousterhout
I have a few outstanding questions from compiling this documentation:
- What's the difference between
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2519#issuecomment-56642802
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20746/consoleFull)
for PR 2519 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2518#issuecomment-56645105
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20745/consoleFull)
for PR 2518 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2518#issuecomment-56645112
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20745/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-56647000
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20747/consoleFull)
for PR 2388 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2519#issuecomment-56649713
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20746/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2519#issuecomment-56649704
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20746/consoleFull)
for PR 2519 at commit
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2520
[SPARK-3677] [BUILD] [YARN] Scalastyle is never applyed to the sources
under yarn/common
You can merge this pull request into a Git repository by running:
$ git pull
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2198#issuecomment-56650781
@tgravescs Thanks for your notification.
I found the issue which causes that scalastyle is not applied to
yarn/common.
I resolved this issue in #2520 .
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56650830
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20748/consoleFull)
for PR 2520 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2508#issuecomment-56651085
@mateiz Got it. On the zip methods, I want to capture the key point from
https://issues.apache.org/jira/browse/SPARK-3098 , that the ordering is not
only not guaranteed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56651140
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20748/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56651137
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20748/consoleFull)
for PR 2520 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56651663
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56652132
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20749/consoleFull)
for PR 2520 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56652447
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20749/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56652443
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20749/consoleFull)
for PR 2520 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2198#issuecomment-56652661
@tgravescs Sorry, I have something wrong. Please wait a little.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-56653261
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20747/consoleFull)
for PR 2388 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-56653270
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20747/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2508#issuecomment-56661626
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20750/consoleFull)
for PR 2508 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-5764
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20751/consoleFull)
for PR 2520 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2508#issuecomment-56669661
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20750/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2508#issuecomment-56669653
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20750/consoleFull)
for PR 2508 at commit
Github user sjbrunst commented on a diff in the pull request:
https://github.com/apache/spark/pull/1717#discussion_r17972016
--- Diff:
external/twitter/src/main/scala/org/apache/spark/streaming/twitter/TwitterUtils.scala
---
@@ -33,15 +33,38 @@ object TwitterUtils {
*
Github user sjbrunst commented on the pull request:
https://github.com/apache/spark/pull/1717#issuecomment-56673018
@tdas The current version of TwitterUtils.scala only has new methods. The
diff makes it look like I changed the original methods, but they are all there.
The original
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56675917
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20751/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56675904
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20751/consoleFull)
for PR 2520 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2333#issuecomment-56677764
Thank you for you work @JoshRosen !
I'll check it out.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2432#issuecomment-56678722
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20752/consoleFull)
for PR 2432 at commit
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/2256#issuecomment-56679585
Hey - I'm traveling at the moment without laptop access, so will be able to
check it out tomorrow evening - hope that's ok :)â
Sent from Mailbox
On Wed, Sep
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2432#issuecomment-56690206
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20752/consoleFull)
for PR 2432 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2432#issuecomment-56690217
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20752/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2513#issuecomment-56690446
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20753/consoleFull)
for PR 2513 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-56694970
I'll merge with master and see if I can reproduce the failure...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-56696661
Yep, fails locally too after the merge. Let me 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
GitHub user jyotiska opened a pull request:
https://github.com/apache/spark/pull/2521
Python SQL Example Code
SQL example code for Python, as shown on [SQL Programming
Guide](https://spark.apache.org/docs/1.0.2/sql-programming-guide.html)
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56698292
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20754/consoleFull)
for PR 2521 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56698293
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20755/consoleFull)
for PR 2520 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56698439
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20754/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56698438
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20754/consoleFull)
for PR 2521 at commit
Github user rnowling commented on the pull request:
https://github.com/apache/spark/pull/2494#issuecomment-56698570
@mengxr doesn't look like the tests started -- maybe Jenkins ignores
comments that address users? Thanks!
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2513#issuecomment-56698729
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20753/consoleFull)
for PR 2513 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2513#issuecomment-56698738
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20753/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56700932
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20756/consoleFull)
for PR 2521 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56700939
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20756/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56700691
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20756/consoleFull)
for PR 2521 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56703017
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20757/consoleFull)
for PR 2521 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2485#issuecomment-56706929
@pwendell @mateiz @andrewor14 can any of you kick jenkins?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2485#issuecomment-56707385
I just kicked it from the `spark-prs` parameterized build trigger; let's
wait and see if it starts...
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2485#issuecomment-56707584
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/146/consoleFull)
for PR 2485 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2485#issuecomment-56707989
ah sorry, looks like something conflicts now and it needs upmerged.
@nishkamravi2 can you please upmerge
---
If your project is set up for it, you can reply
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2521#discussion_r17987196
--- Diff: examples/src/main/python/sql.py ---
@@ -0,0 +1,52 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+#
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56709666
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20755/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56709659
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20755/consoleFull)
for PR 2520 at commit
Github user jyotiska commented on a diff in the pull request:
https://github.com/apache/spark/pull/2521#discussion_r17987266
--- Diff: examples/src/main/python/sql.py ---
@@ -0,0 +1,52 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+#
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-56709844
I found the problem - it was caused by a recent PR that basically broke
yarn-cluster mode...
---
If your project is set up for it, you can reply to this email and have
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56710085
This example only demonstrate jsonFile(), it will more powerful if it could
have some usage of `inferSchema()` and `applySchema()`.
---
If your project is set up for it,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-56710658
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20758/consoleFull)
for PR 2257 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2257#discussion_r17987981
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -401,17 +401,17 @@ private[spark] class
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-56711425
LGTM. I don't really understand why you need to tell sbt again where the
sources are (after all, sbt does build the yarn code properly), but then I'm
not an sbt expert.
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-56711888
Ah good catch. The latest changes LGTM if you get the tests to pass.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56713322
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20757/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2521#issuecomment-56713314
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20757/consoleFull)
for PR 2521 at commit
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/2522
[SPARK-3679] [PySpark] pickle the exact globals of functions
function.func_code.co_names has all the names used in the function,
including name of attributes. It will pickle some unnecessary globals
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2512#issuecomment-56717149
Looks good - thanks Nick.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2478#issuecomment-56717218
I think `len(rdd)` has the potential to be confused with `rdd.count()`,
since calling `len()` on a Python collection usually returns the size of that
collection.
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2510#issuecomment-56717292
Looks good, thanks Shivaram. I'll merge 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2522#issuecomment-56717278
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20759/consoleFull)
for PR 2522 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2512
---
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 elmalto opened a pull request:
https://github.com/apache/spark/pull/2523
logNormalGraph missing partition parameter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/elmalto/spark patch-1
Alternatively you can review
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2507#issuecomment-56717540
Hey can you create a JIRA issue for this? Also, can you add [GraphX] to the
title? Thanks /cc @ankurdave
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2510
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2523#issuecomment-56717691
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 project
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2492#discussion_r17991203
--- Diff: python/pyspark/context.py ---
@@ -183,10 +183,9 @@ def _do_init(self, master, appName, sparkHome,
pyFiles, environment, batchSize,
1 - 100 of 362 matches
Mail list logo
