Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-52146688
QA tests have started for PR 1321. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18523/consoleFull
---
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-52146302
:)
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-52146296
Now I think about it more. LGTM.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-52146322
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-48999051
@rxin is there a case where you think local execution will yield a relevant
performance improvement? I don't see why shopping a task for a few milliseconds
is a bit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-48999161
When the cluster is busy and backlogged ...
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-49002113
I think it makes more sense if you can't run a command than certain
commands happen to be runnable while there are no cluster resources. This sort
of execution puts
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-48280965
Maybe we should also solve the problem that local execution should not
transfer the whole in-memory block (as a matter of fact, perhaps local
execution should just bypass
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1321#issuecomment-48242188
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/1321#issuecomment-48242208
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/1321#issuecomment-48250513
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
11 matches
Mail list logo
