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?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
