zhuzhurk opened a new pull request #10237: [FLINK-14362][runtime] Change 
DefaultSchedulingResultPartition to return correct partition state
URL: https://github.com/apache/flink/pull/10237
 
 
   
   ## What is the purpose of the change
   
   This PR makes a clearer definition of ResultPartitionState as:
   - CREATED // partition is just created or is just reset
   - CONSUMABLE // pipelined partition has data produced or blocking 
partition's parent result finishes. Corresponds to 
IntermediateResultPartition#isConsumable.
   
   The DefaultResultPartition is also fixed to return ResultPartitionState 
based the true partition state, rather than the vertex state.
   
   ## Brief change log
   
     - *Refactored ResultPartitionState*
     - *Fixed DefaultResultPartition*
   
   ## Verifying this change
   
   
   This change added tests and can be verified as follows:
     - *Adjusted unit tests for DefaultResultPartition and  
DefaultExecutonTopology*
   
   ## 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