We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If I don't set SPARK_HOME and I don't have spark-submit on my PATH, then adam-submit errors out early:
SPARK_HOME
spark-submit
PATH
adam-submit
$ bin/adam-submit Using ADAM_MAIN=org.bdgenomics.adam.cli.ADAMMain
I believe it's because the subshell call to which spark-submit returns an error code and adam-submit calls set -e.
which spark-submit
set -e
The text was updated successfully, but these errors were encountered:
cc @heuermh
Sorry, something went wrong.
I thought you were the bash expert? ;) I can confirm this happens on HEAD.
After further investigation it doesn't appear to be caused by anything I added recently. Commenting out set -e does the trick, what is that for?
[ADAM-857] Corrected handling of env vars in bin scripts
5c275c6
Because of `set -e`, the `which spark-submit` subshell command was causing the script to exit early. Fixes bigdatagenomics#857.
No branches or pull requests
If I don't set
SPARK_HOME
and I don't havespark-submit
on myPATH
, thenadam-submit
errors out early:I believe it's because the subshell call to
which spark-submit
returns an error code andadam-submit
callsset -e
.The text was updated successfully, but these errors were encountered: