zhuzhurk opened a new pull request #9797: [FLINK-14059][core] Introduce option 
allVerticesInSameSlotSharingGroupByDefault in ExecutionConfig
URL: https://github.com/apache/flink/pull/9797
 
 
   
   ## What is the purpose of the change
   
   This PR is to introduce option allVerticesInSameSlotSharingGroupByDefault in 
ExecutionConfig.
   It's true by default for DataSet and streaming jobs so that tasks can be 
scheduled with slots not fewer than the max parallelism.
   It's false for blink batch jobs so that vertices can we can have finer 
resource planning regarding pipelined regions.
   
   
   ## Brief change log
   
   *(for example:)*
     - *Introduced option allVerticesInSameSlotSharingGroupByDefault in 
ExecutionConfig. The default value is true.*
     - *Set the option to false for blink batch jobs*
   
   
   ## Verifying this change
   
   
     - *Added unit tests for blink batch job generation*
   
   ## 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 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:
[email protected]


With regards,
Apache Git Services

Reply via email to