[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595550#comment-14595550
]
ASF GitHub Bot commented on FLINK-2161:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/805#issuecomment-114046659
To add more jars to the Classpath, you can write the test in the following
way: The test itself is just a wrapper that instantiates a custom classloader
with your extra class files. It will the load the test class with
Class.forName(classname, true, createdClassLoader).
That way, the test has the extra classes available...
> Flink Scala Shell does not support external jars (e.g. Gelly, FlinkML)
> ----------------------------------------------------------------------
>
> Key: FLINK-2161
> URL: https://issues.apache.org/jira/browse/FLINK-2161
> Project: Flink
> Issue Type: Improvement
> Reporter: Till Rohrmann
> Assignee: Nikolaas Steenbergen
>
> Currently, there is no easy way to load and ship external libraries/jars with
> Flink's Scala shell. Assume that you want to run some Gelly graph algorithms
> from within the Scala shell, then you have to put the Gelly jar manually in
> the lib directory and make sure that this jar is also available on your
> cluster, because it is not shipped with the user code.
> It would be good to have a simple mechanism how to specify additional jars
> upon startup of the Scala shell. These jars should then also be shipped to
> the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
