ifndef-SleePy opened a new pull request #8985: [FLINK-13101][datastream] 
Introduce blockingAfterChainingOff property of StreamGraph
URL: https://github.com/apache/flink/pull/8985
 
 
   ## What is the purpose of the change
   
   * **This is based on https://github.com/apache/flink/pull/8982**
   
   * The reason of introducing it is to satisfy the requirement of Blink batch 
planner.
   * Because the current scheduling strategy is a bit simple. It can not 
support some complex scenarios, like a batch job with resources limited.
   * To be honest, it's probably a work-around solution. However it's an 
internal implementation, we can replace it when we are able to support batch 
job by scheduling strategy.
   
   ## Brief change log
   
   * Add a property `blockingAfterChainingOff` of `StreamGraph`
   * The property "blocking after chaining off" means, if there are some stream 
edges that can not be chained and the shuffle mode of edge is not specified, 
translate these edges into `BLOCKING` result partition type.
   
   ## Verifying this change
   
   * This change added unit tests
   
   ## 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)`: no
     - 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**
     - If yes, how is the feature documented? **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:
[email protected]


With regards,
Apache Git Services

Reply via email to