GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/1736
[Minor] Fixes on top of #1679
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark amend-#1679
Alternatively you can review and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1736#issuecomment-50956861
QA tests have started for PR 1736. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17762/consoleFull
---
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1736#discussion_r15728056
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerSource.scala ---
@@ -46,9 +46,8 @@ private[spark] class BlockManagerSource(val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1736#issuecomment-50957930
QA results for PR 1736:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1736#discussion_r15730250
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerSource.scala ---
@@ -46,9 +46,8 @@ private[spark] class BlockManagerSource(val
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1736#discussion_r15732438
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerSource.scala ---
@@ -46,9 +46,8 @@ private[spark] class BlockManagerSource(val
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1736#discussion_r15732470
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerSource.scala ---
@@ -46,9 +46,8 @@ private[spark] class BlockManagerSource(val
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1736
---
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
