GitHub user kayousterhout opened a pull request:
https://github.com/apache/spark/pull/39
Remote BlockFetchTracker trait
This trait seems to have been created a while ago when there
were multiple implementations; now that there's just one, I think it
makes sense to merge it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/39#issuecomment-36305800
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/39#issuecomment-36307824
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12922/
---
If your project
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/39#discussion_r10152243
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockFetcherIterator.scala ---
@@ -44,9 +44,14 @@ import org.apache.spark.util.Utils
*/
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/39#discussion_r10152493
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockFetcherIterator.scala ---
@@ -233,7 +238,16 @@ object BlockFetcherIterator {
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/39#issuecomment-36323841
Thanks @pwendell -- fixed the style!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/39
---
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
