You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/06/07 13:02:31 UTC

[GitHub] [flink] 1u0 opened a new pull request #8660: [FLINK-12143]

1u0 opened a new pull request #8660: [FLINK-12143]
URL: https://github.com/apache/flink/pull/8660
 
 
   ## What is the purpose of the change
   
   This PR changes Flink distribution's starter scripts: defines new configuration environment parameter for plugins dir and passes the configuration to the plugins manager.
   
   Currently, only file system components support the plugin manager, so related (to file system) end-to-end tests also have been modified to be loaded via the plugin manager.
   
   ## Brief change log
   
     - the scripts in `flink-dist` have been modified, a new `FLINK_HOME` environment variable replaces `FLINK_ROOT_DIR`;
     - the various Flink startup entry points are extended to configure and pass plugins dir to plugins manager;
     - the plugin manager is configured by system wide parents first patterns for class loading;
    - some end-to-end tests involving different file system components are modified to use fs components via plugins mechanism.
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as:
    - e2e batch wordcount tests for hadoop, presto, azure and dummy fs are modified to use the corresponding fs component via plugin mechanism;
    - `test_streaming_file_sink.sh` is modified to use hadoop fs via plugin mechanism;
    - `test_docker_embedded_job.sh` is modified to use dummy fs via plugin mechanism;
    - `test_yarn_kerberos_docker.sh` is modified to use dummy fs via plugin mechanism. 
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (**yes** / no) (the distribution Flink scripts)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (**yes** / no / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / no)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services