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/07/02 12:35:55 UTC

[GitHub] [flink] ifndef-SleePy opened a new pull request #8946: [FLINK-13042][datastream] Make slot sharing configurable on StreamExecutionEnvironment

ifndef-SleePy opened a new pull request #8946: [FLINK-13042][datastream] Make slot sharing configurable on StreamExecutionEnvironment
URL: https://github.com/apache/flink/pull/8946
 
 
   ## What is the purpose of the change
   
   * There is a requirement of Blink batch planner that providing a global setting that disabling slot sharing. To support that, will expose a `PublicEvolving` method on `StreamExecutionEnvironment` to globally disable slot sharing.
   
   * Note that, this method might be removed if there is a better approach to satisfy Blink batch planner in the future.
   
   * There is a discussion under https://github.com/apache/flink/pull/8931 at the moment
   * **This PR should not go forward until there is an agreement reached**
   
   ## Brief change log
   
   * Add a `PublicEvolving` method on `StreamExecutionEnvironment` to enable/disable slot sharing
   
   ## Verifying this change
   
   * Added integration tests to verify slot sharing behavior
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: **yes**
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **yes** maybe
     - If yes, how is the feature documented? **docs & JavaDocs**
   

----------------------------------------------------------------
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