Class RemoteEnvironment


  • @Deprecated
    @Public
    public class RemoteEnvironment
    extends ExecutionEnvironment
    Deprecated.
    All Flink DataSet APIs are deprecated since Flink 1.18 and will be removed in a future Flink major version. You can still build your application in DataSet, but you should move to either the DataStream and/or Table API.
    An ExecutionEnvironment that sends programs to a cluster for execution. The environment needs to be created with the address and port of the JobManager of the Flink cluster that should execute the programs.

    Many programs executed via the remote environment depend on additional classes. Such classes may be the classes of functions (transformation, aggregation, ...) or libraries. Those classes must be attached to the remote environment as JAR files, to allow the environment to ship the classes into the cluster for the distributed execution.

    See Also:
    FLIP-131: Consolidate the user-facing Dataflow SDKs/APIs (and deprecate the DataSet API
    • Constructor Detail

      • RemoteEnvironment

        public RemoteEnvironment​(String host,
                                 int port,
                                 String... jarFiles)
        Deprecated.
        Creates a new RemoteEnvironment that points to the master (JobManager) described by the given host name and port.

        Each program execution will have all the given JAR files in its classpath.

        Parameters:
        host - The host name or address of the master (JobManager), where the program should be executed.
        port - The port of the master (JobManager), where the program should be executed.
        jarFiles - The JAR files with code that needs to be shipped to the cluster. If the program uses user-defined functions, user-defined input formats, or any libraries, those must be provided in the JAR files.
      • RemoteEnvironment

        public RemoteEnvironment​(String host,
                                 int port,
                                 org.apache.flink.configuration.Configuration clientConfig,
                                 String[] jarFiles)
        Deprecated.
        Creates a new RemoteEnvironment that points to the master (JobManager) described by the given host name and port.

        Each program execution will have all the given JAR files in its classpath.

        Parameters:
        host - The host name or address of the master (JobManager), where the program should be executed.
        port - The port of the master (JobManager), where the program should be executed.
        clientConfig - The configuration used by the client that connects to the cluster.
        jarFiles - The JAR files with code that needs to be shipped to the cluster. If the program uses user-defined functions, user-defined input formats, or any libraries, those must be provided in the JAR files.
      • RemoteEnvironment

        public RemoteEnvironment​(String host,
                                 int port,
                                 org.apache.flink.configuration.Configuration clientConfig,
                                 String[] jarFiles,
                                 URL[] globalClasspaths)
        Deprecated.
        Creates a new RemoteEnvironment that points to the master (JobManager) described by the given host name and port.

        Each program execution will have all the given JAR files in its classpath.

        Parameters:
        host - The host name or address of the master (JobManager), where the program should be executed.
        port - The port of the master (JobManager), where the program should be executed.
        clientConfig - The configuration used by the client that connects to the cluster.
        jarFiles - The JAR files with code that needs to be shipped to the cluster. If the program uses user-defined functions, user-defined input formats, or any libraries, those must be provided in the JAR files.
        globalClasspaths - The paths of directories and JAR files that are added to each user code classloader on all nodes in the cluster. Note that the paths must specify a protocol (e.g. file://) and be accessible on all nodes (e.g. by means of a NFS share). The protocol must be supported by the URLClassLoader.