Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47301407
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16180/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47301406
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16177/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47301403
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/1240#issuecomment-47301408
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16181/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47301402
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 witgo closed the pull request at:
https://github.com/apache/spark/pull/1112
---
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 witgo reopened a pull request:
https://github.com/apache/spark/pull/1112
SPARK-1291: Link the spark UI to RM ui in yarn-client mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-1291
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47301659
close temporarily
---
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/1190
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47301657
Thanks, merged into master.
---
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 closed the pull request at:
https://github.com/apache/spark/pull/1240
---
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 colorant opened a pull request:
https://github.com/apache/spark/pull/1241
[SPARK-2288] Hide ShuffleBlockManager behind ShuffleManager
By Hiding the shuffleblockmanager behind Shufflemanager, we decouple the
shuffle data's block mapping management work from
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47301718
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47301721
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47301712
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/1112#issuecomment-47301713
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 marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277491
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output:
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277496
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output:
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277517
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output:
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277569
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -204,3 +204,17 @@ case class ExistingRdd(output:
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277596
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -614,6 +614,8 @@ private[hive] object HiveQl {
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302051
This implementation is looking pretty complete. :)
A few testing and stylistic comments before we can merge this. Also please
merge with master.
---
If your
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302075
ok to test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277643
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -614,6 +614,8 @@ private[hive] object HiveQl {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47302192
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/1200#issuecomment-47302205
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/1241#issuecomment-47302193
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16183/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302186
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1200#issuecomment-47302206
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16182/
---
If your project is set up for it, you can
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1151#discussion_r14277706
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -614,6 +614,8 @@ private[hive] object HiveQl {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302616
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/1151#issuecomment-47302606
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/1151#issuecomment-47302612
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302617
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16185/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302695
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16186/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302694
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/1151#issuecomment-47302828
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/1151#issuecomment-47302830
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302898
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/1151#issuecomment-47302899
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16187/
---
If your project is set up for it, you can
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47302963
Hi Michael, adrian-wang ,Thanks a lot ,I have update all the files as
your suggestion!
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47303045
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1147#issuecomment-47303041
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/1147#issuecomment-47303051
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47303127
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/1151#issuecomment-47303129
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16188/
---
If your project is set up for it, you can
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-47303095
Hi all,What should i do next ! 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
GitHub user CodingCat reopened a pull request:
https://github.com/apache/spark/pull/1240
SPARK-2126: Move MapOutputTracker behind ShuffleManager interface to
https://issues.apache.org/jira/browse/SPARK-2126
Move MapOutputTracker behind ShuffleManager interface to enable
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47303487
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/1241#issuecomment-47303494
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47303498
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47303576
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/1112#issuecomment-47303577
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16184/
---
If your
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1241#discussion_r14278746
--- Diff: core/src/main/scala/org/apache/spark/shuffle/ShuffleManager.scala
---
@@ -50,7 +50,9 @@ private[spark] trait ShuffleManager {
context:
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/1216#issuecomment-47306081
instead of set +e/-e, i'd suggest git rev-parse || : and then construct
the GITREVSTRING on a positive test -n result
however, the code works as presented
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47306230
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47306226
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/1217#issuecomment-47306295
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16192/
---
If your project is set up for it, you can
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1227#issuecomment-47306288
Ok I'm going to merge this in master.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47306294
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/1236#discussion_r14279017
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -391,7 +395,7 @@ private[spark] class TaskSetManager(
}
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1236#issuecomment-47306344
Ok merging this in master. Thanks for reviewing!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1236
---
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 rahulsinghaliitd commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47306598
Tested successfully that the UI URL is correctly displayed in RM UI and
that the spark UI is correctly rendered.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47306603
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/1217#issuecomment-47306606
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47306664
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16193/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47306663
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 rahulsinghaliitd commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14279134
--- Diff: core/src/main/scala/org/apache/spark/ui/UIUtils.scala ---
@@ -135,7 +135,16 @@ private[spark] object UIUtils extends Logging {
}
Github user rahulsinghaliitd commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14279155
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,20 @@ class ExecutorLauncher(args:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1147#issuecomment-47307221
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/1241#issuecomment-47307223
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16190/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1241#issuecomment-47307220
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/1240#issuecomment-47307222
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/1147#issuecomment-47307224
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16189/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47307225
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16191/
---
If your
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47307463
@pwendell @markhamstra
Hi, Patrick and Mark, I submitted this version of PR, expect your feedbacks!
---
If your project is set up for it, you can reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1237#issuecomment-47307523
Would you mind creating a JIRA for this and formatting the title correctly?
See the green box here - thanks!
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47307525
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/1240#issuecomment-47307529
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1229
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/1135
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1135#issuecomment-47308127
Thanks 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
Github user colorant commented on a diff in the pull request:
https://github.com/apache/spark/pull/1241#discussion_r14279781
--- Diff:
core/src/main/scala/org/apache/spark/shuffle/ShuffleBlockManager.scala ---
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1147#issuecomment-47308393
Thanks @marmbrus merged some of the dependent PRs. I've also updated both
code and description for this PR accordingly, some of the issues were listed in
the PR
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1242
[SPARK-2304] tera sort example program for shuffle benchmarks
This pull request adds an example program for benchmarking Spark shuffle.
It dynamically generates a set of 100 byte records according to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1242#issuecomment-47308594
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1242#issuecomment-47308593
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/1242#issuecomment-47308636
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16195/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1242#issuecomment-47308635
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1236#issuecomment-47308711
Hey @rxin I was wondering -- is the TID useless now that the UI shows the
attempt #?
---
If your project is set up for it, you can reply to this email and have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1236#issuecomment-47308828
It's going to be useless if we stop using them in logs. I think right now
they might still be useful since they can be used to correlate with log
messages.
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1242#issuecomment-47308992
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1242#issuecomment-47308985
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 li-zhihui commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r14279974
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClusterSchedulerBackend.scala
---
@@ -0,0 +1,39 @@
+/*
+ * Licensed to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47309162
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16194/
---
If your
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/962#discussion_r14280009
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -39,6 +40,13 @@ private[spark] case class ByteBufferValues(buffer:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1240#issuecomment-47309161
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 kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/962#discussion_r14280013
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -457,12 +467,12 @@ private[spark] class BlockManager(
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/962#discussion_r14280023
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala ---
@@ -69,6 +71,12 @@ private[ui] class StagePage(parent: JobProgressTab)
301 - 400 of 408 matches
Mail list logo
