take-it-out opened a new pull request, #20484:
URL: https://github.com/apache/flink/pull/20484

   ## What is the purpose of the change
   
   During restore from changelog state backend , the native checkpoint could 
contain the relative file state handles (which size is greater than 
`state.storage.fs.memory-threshold`), file path in these file state handles 
would be resolve as relative which leads to FileNotFoundException.
   
   File path in IncrementalKeyedStateHandle should be cast to absolute path 
during restore, so that the correct file path will be read.
   
   
   ## Brief change log
   
   cast file path to absolute path in IncrementalRemoteKeyedStateHandle during 
restore in changelog state backend.
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as 
*org.apache.flink.test.checkpointing.ChangelogPeriodicMaterializationSwitchStateBackendITCase*.
  (`state.storage.fs.memory-threshold` is reduced)
   
   ## 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, 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to