[
https://issues.apache.org/jira/browse/FLINK-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588259#comment-14588259
]
ASF GitHub Bot commented on FLINK-2161:
---------------------------------------
Github user nikste commented on the pull request:
https://github.com/apache/flink/pull/805#issuecomment-112477088
Changed according to comments,
@tillrohrmann I did not check it on a cluster, since I don't have one
available at the moment. I checked with a local jobmanager (using
"start-local.sh"), that seemed to work. Maybe you can check if it works with a
remote cluster as well?
Concerning automated tests, its somewhat tricky. The jar has to be sent to
the remote execution and at the same time be available in the shell. You cant
add jars from inside the shell (scala 2.10
bug:https://issues.scala-lang.org/browse/SI-6502), only at startup with an
additional parameter (see bash script: start-scala-shell.sh).
If I try to invoke the start-scala-shell.sh script from inside java/scala
and redirect the std out I only get half of the output (everything till the
actual scala shell starts).
Is it possible to add an additional classpath in maven for the tests? Then
at least I could write a test, that checks if the jars are shipped to the
remote environment..
Or do you have another suggestion maybe?
> 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)
