[
https://issues.apache.org/jira/browse/LIVY-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-487:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Livy remote jars and files incorrectly specified on classpath
> -------------------------------------------------------------
>
> Key: LIVY-487
> URL: https://issues.apache.org/jira/browse/LIVY-487
> Project: Livy
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.5.0
> Reporter: Tim Harsch
> Priority: Critical
> Fix For: 0.10.0
>
>
> From a thread in users-livy group:
> If I submit jars using a client machine that is not the same as the server
> (so file system is not shared) and I submit the jar it’s looks like it gets
> transmitted to the server but then I can’t reference any of the classes. *If
> I look at the Spark UI that gets launched for the session then I can see
> references to paths in my client machine*, which aren’t resolvable on the
> server. Is this the scenario you have? I think it might occur in a docker
> env if you are doing client stuff on the host os, and livy is running in a
> container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
