Github user ngbinh commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449390
Yep, found the problem now. Should be fixed!
---
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 ngbinh commented on the pull request:
https://github.com/apache/spark/pull/41#issuecomment-36449199
just add Author to both PR and the commit.
---
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 ngbinh opened a pull request:
https://github.com/apache/spark/pull/41
Update io.netty from 4.0.13 Final to 4.0.17.Final
This update contains a lot of bug fixes and some new perf improvements.
It is also binary compatible with the current 4.0.13.Final
For
Github user ngbinh commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36292181
@pwendell Yes! You can point to https://github.com/ngbinh/spark-vagrant
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user ngbinh closed the pull request at:
https://github.com/apache/spark/pull/26
---
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 ngbinh commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36279863
@pwendell makes sense! I will maintain this on its own repo. Close for now!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user ngbinh reopened a pull request:
https://github.com/apache/spark/pull/26
[SPARK-1146] Vagrant support for Spark
This PR uses Vagrant to create a clusters of three VMs, one master and two
workers. It allows running/testing Spark Cluster mode on one machine.
My
Github user ngbinh closed the pull request at:
https://github.com/apache/spark/pull/26
---
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 ngbinh commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36275658
Thanks for reminding me.
---
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 ngbinh commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36226895
One of the main reason I work on this PR is I found many times working on
Spark local mode doesn't expose problems when deployed on a cluster. This PR
should allow
Github user ngbinh commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36226574
I can argue that having ec2, stand alone cluster scripts inside the core
repo is important for Spark adoption.
@markhamstra I agree. My feeling is the benefit is
Github user ngbinh commented on the pull request:
https://github.com/apache/spark/pull/26#issuecomment-36226015
I agree that while they are not necessary be a part of Spark core because
there is usually no direct dependencies between them. But I feel like they make
Spark more
GitHub user ngbinh opened a pull request:
https://github.com/apache/spark/pull/26
Vagrant support for Spark
This PR uses Vagrant to create a clusters of three VMs, one master and two
workers. It allows running/testing Spark Cluster mode on one machine.
My initial goal is
13 matches
Mail list logo
