[
https://issues.apache.org/jira/browse/FLINK-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585692#comment-14585692
]
ASF GitHub Bot commented on FLINK-2209:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/835#discussion_r32403522
--- Diff: docs/apis/cluster_execution.md ---
@@ -80,67 +80,73 @@ Note that the program contains custom user code and
hence requires a JAR file wi
the classes of the code attached. The constructor of the remote environment
takes the path(s) to the JAR file(s).
-## Remote Executor
+## Linking with modules not contained in the binary distribution
-Similar to the RemoteEnvironment, the RemoteExecutor lets you execute
-Flink programs on a cluster directly. The remote executor accepts a
-*Plan* object, which describes the program as a single executable unit.
+The binary distribution contains jar packages in the `lib` folder that are
automatically
+provided to the classpath of your distrbuted programs. Almost all of Flink
classes are
+located there with a few exceptions, for example the streaming connectors
and some freshly
+added modules. To run code depending on these modules you need to make
them accessible
--- End diff --
Why listing the streaming connectors and not the other libraries? Maybe we
can list/link all of them here.
> Document how to use TableAPI, Gelly and FlinkML, StreamingConnectors on a
> cluster
> ---------------------------------------------------------------------------------
>
> Key: FLINK-2209
> URL: https://issues.apache.org/jira/browse/FLINK-2209
> Project: Flink
> Issue Type: Improvement
> Reporter: Till Rohrmann
> Assignee: Márton Balassi
>
> Currently the TableAPI, Gelly, FlinkML and StreamingConnectors are not part
> of the Flink dist module. Therefore they are not included in the binary
> distribution. As a consequence, if you want to use one of these libraries the
> corresponding jar and all their dependencies have to be either manually put
> on the cluster or the user has to include them in the user code jar.
> Usually a fat jar is built if the one uses the quickstart archetypes. However
> if one sets the project manually up this ist not necessarily the case.
> Therefore, it should be well documented how to run programs using one of
> these libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
