[jira] [Commented] (TOREE-308) Interpreter jar not found

["Gino Bustelo (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TOREE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262102#comment-15262102 ] 

Gino Bustelo commented on TOREE-308:
------------------------------------

I always found it strange that we needed to pass the TOREE_ASSEMBLY to the `--driver-class-path` option. I would have expected the spark submit process to figure that out. Before we do any work of adding yet another ENV variable, we need to check if Toree can start correctly without passsing the TOREE_ASSEMBLY to the `--driver-class-path` and leave that option totally free for external configuration through SPARK_OPTS.

> 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
>
> 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)