Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/604#issuecomment-48366967
Did you mean to close this PR?
---
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 ha
Github user sarutak closed the pull request at:
https://github.com/apache/spark/pull/604
---
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 enab
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/604#issuecomment-42373680
Thank you for your comment, mridulm!
I will revise the patch.
I met the bug when I remove the block files in /tmp/spark-local-*/ on the
local filesystem of an
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/604#issuecomment-4256
Can you add a testcase to verify this ?
Where None is returned and validated.
I suspect we have also observed in the past too - but I never got around to
naili
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/604#discussion_r12257245
--- Diff:
core/src/main/scala/org/apache/spark/storage/DiskBlockManager.scala ---
@@ -71,13 +71,13 @@ private[spark] class DiskBlockManager(shuffleManager:
Sh
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/604#discussion_r12257233
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockFetcherIterator.scala ---
@@ -203,14 +203,22 @@ object BlockFetcherIterator {
// these a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/604#issuecomment-41866556
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 proj
