SteNicholas opened a new pull request #15729:
URL: https://github.com/apache/flink/pull/15729


   ## What is the purpose of the change
   
   *Savepoints are currently read when the `ExecutionGraph` is created. This is 
causing problems when determining the (max) parallelism the job is run with, 
because the savepoint may impose additional restrictions. This caused quite a 
few headaches in FLINK-21844, and further requires the execution vertices to 
have a mutable max parallelism. `DefaultExecutionGraphFactory` should load the 
savepoint and then extract from it potential constraints for the 
`ExecutionGraph` creation.*
   
   ## Brief change log
   
     - *Separate `Checkpoints.loadAndValidateCheckpoint` into 
`Checkpoints.loadCheckpoint` and `Checkpoints.validateCheckpoint` for loading 
the savepoint before the `ExecutionGraph` creation.*
   
   ## Verifying this change
   
     - *`CheckpointMetadataLoadingTest` updates 
`Checkpoints.loadAndValidateCheckpoint` to `Checkpoints.loadCheckpoint` and 
`Checkpoints.validateCheckpoint`.*
   
   ## 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, Kubernetes/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:
us...@infra.apache.org


Reply via email to