[
https://issues.apache.org/jira/browse/TOREE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262191#comment-15262191
]
Phil Berkland commented on TOREE-308:
-------------------------------------
The main goal is we want our interpreter class found by toree. It used to be
found when we used SPARK_OPT --jars. It was by trial and error that I
discovered the interpreter would be found by using --driver-class-path. If
there is some other option than using --driver-class-path, we could use that.
> Interpreter jar not found
> -------------------------
>
> Key: TOREE-308
> URL: https://issues.apache.org/jira/browse/TOREE-308
> Project: TOREE
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Phil Berkland
> Fix For: 0.1.0
>
>
> We previously added our interpreter plugin by adding
> "SPARK_OPTS": "--jars file:/path/to/our.jar",
> to kernel.json.
> This no longer works, we get a message that the interpreter was not found.
> We discovered if we modified the --driver-class-path in toree/run.sh to
> include our jar, the interpreter was found.
> SPARK_OPTS="--driver-class-path=\"${TOREE_ASSEMBLY}:/path/to/our.jar\"
> ${SPARK_OPTS}"
> Unfortunately, this cannot be specified in the kernel.json, because the
> TOREE_ASSEMBLY would be lost.
> A new ENV var could be added (i.e. TOREE_DRIVER_JAR)
>
> SPARK_OPTS="--driver-class-path=\"${TOREE_ASSEMBLY}:${TOREE_DRIVER_JAR}:\"
> ${SPARK_OPTS}"
> which we could specifiy in our kernel.json
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
