Skip to content
New issue

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

Can't work with spark #295

Open
nonlinearthink opened this issue May 21, 2020 · 1 comment · May be fixed by #430
Open

Can't work with spark #295

nonlinearthink opened this issue May 21, 2020 · 1 comment · May be fixed by #430
Milestone

Comments

@nonlinearthink
Copy link

nonlinearthink commented May 21, 2020

I'm a beginner in Data Science.

Before that, I used jenv to manage multiple Java versions, but when I used spark, I found that spark couldn't run.

CLI reports an error as follows:

/usr/local/spark/bin/spark-class: line 99: /Users/jayceechow/.jenv/versions/system/bin/java: No such file or directory
/usr/local/spark/bin/spark-class: line 99: exec: /Users/jayceechow/.jenv/versions/system/bin/java: cannot execute: No such file or directory

I guess this may be caused by jenv, so I uninstalled jenv and deleted the related content of .zshrc, and now spark is running well.

I think jenv is great. I hope it can be solved.

@andrewflbarnes
Copy link
Contributor

This is a problem when using system as the version for java. In that case the export plugin erroneously sets JAVA_HOME to $JENV_ROOT/versions/system which does not exist.

#422 should resolve this - once merge in you would then be able to set JAVA_HOME for spark to pick up. e.g.

jenv shell 17
# do some stuff
jenv shell system
export JAVA_HOME=/path/to/java/home
spark ...

Alternatively setting an explicit version should work correctly e.g.

jenv shell 11
spark ...

@andrewflbarnes andrewflbarnes added this to the 0.5.8 milestone Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants