Github user nishkamravi2 closed the pull request at:
https://github.com/apache/spark/pull/492
---
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 nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-53905298
Ok, closed.
---
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
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-53890256
can we close this now? We have a 1.x branch now with spark-submit and
will have a 1.1 release relatively soon. If someone really needs this in the
0.9.x line they can
Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-48769703
@tgravescs Sorry, missed this one somehow. Yes, spark-submit is now fully
tested. We could keep this one open for 0.92 potentially.
---
If your project is set up fo
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-45633823
@nishkamravi2 have you tried the spark-submit script and can we close
this?
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41964634
Spark-submit looks neat and it does make sense to encourage use of a single
primary interface for Spark invocation. Whether or not there is value in
cleaning up the s
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41926941
> --driver-java-options would only work through the spark-submit script.
>
Correct, and as Patrick mentions, it should be the way to submit spark jobs
going
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41890440
@nishkamravi2 hey, the older yarn client is being deprecated so we probably
won't add new features to it. That is, if users want to take advantage of new
options they wil
Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41882773
--driver-java-options would only work through the spark-submit script. If
the developer invokes yarn.deploy.Client directly (as is common practice
thusfar), they woul
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41862363
I think this is (now) already available as "--driver-java-options" (works
both for yarn-client and yarn-cluster modes).
---
If your project is set up for it, you can reply
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41157756
see the comment on the jira. Also things should generally flow through the
spark-submit script now.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/492#issuecomment-41116321
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
GitHub user nishkamravi2 opened a pull request:
https://github.com/apache/spark/pull/492
SPARK-1576 (Allow JAVA_OPTS to be passed as a command line parameter to
YARN client)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nishka
13 matches
Mail list logo
