[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577091#comment-14577091
]
ASF GitHub Bot commented on FLINK-2161:
---------------------------------------
GitHub user nikste opened a pull request:
https://github.com/apache/flink/pull/805
[FLINK-2161] modified Scala shell start script to take additional argument
(-cp or --classpath…
…) for external libraries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nikste/flink Scala_shell_external_jar
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/805.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #805
----
commit 80ad72c05bb27413be98271ff16c907a7bc3a0e8
Author: Nikolaas Steenbergen <[email protected]>
Date: 2015-06-08T12:01:39Z
[FLINK-2161] modified start script to take additional argument (-cp or
--classpath) for external libraries
----
> 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)
