flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mbalassi <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-2209] Document linking with jars not in...
Date Mon, 15 Jun 2015 09:30:47 GMT
Github user mbalassi commented on a diff in the pull request:

    --- 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
    +during runtime, for which we suggest two options:
    -### Maven Dependency
    -If you are developing your program in a Maven project, you have to add the
    -`flink-clients` module using this dependency:
    -  <groupId>org.apache.flink</groupId>
    -  <artifactId>flink-clients</artifactId>
    -  <version>{{ site.version }}</version>
    -### Example
    -The following illustrates the use of the `RemoteExecutor` with the Scala API:
    -def main(args: Array[String]) {
    -    val input = TextFile("hdfs://path/to/file")
    +1. Either copy the required jar files to the `lib` folder onto all of your TaskManagers.
    --- End diff --

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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message