-
Bug
-
Resolution: Unresolved
-
Major
-
None
Hi loghijiaha,
I'm debugging the plug-in just to have one final look at the code as we are near the end of GSoC.
While doing so, I found what seems to be a bug.
My job has several build steps, one for JS, one for Python, etc. The one for JS triggers the following pre-command, which I think is being used to change the working directory.
import os os.chdir('/home/kinow/Development/java/jenkins/machine-learning-plugin/work/workspace/e2e-1')
That results in an error, that is logged as "ERROR'. I tested using `%%python` in a notebook cell, while using the same javascript kernel, but it still failed to run. This command only works when I select the Python kernel.
I wonder if there is no way to tell Zeppelin what is the working directory we want to use, before starting the kernel?
- links to
I think Zeppelin moves some Python files to a newly created temporary directory. Then executes the Kernel over there. Might be an option too. Instead of trying to tell the Kernel to use the workspace as working directory, copy the files over to where the Kernel is running? That would probably require more time investigating and testing.
https://github.com/apache/zeppelin/blob/51a23801b38eb76f4e72c21304136c6090d4b808/zeppelin-jupyter-interpreter/src/main/java/org/apache/zeppelin/jupyter/JupyterKernelInterpreter.java#L182