[
https://issues.apache.org/jira/browse/FLINK-34652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hangxiang Yu updated FLINK-34652:
---------------------------------
Description:
As discussed before, we may consider supporting CheckpointStreamFactory for
StateChangeFsUploader:
* need for checkpointId in the current API to resolve the location
* different settings for materialized/changelog (e.g. timeouts)
* re-use closeAndGetHandle
* re-use in-memory handles (.metadata)
* handle in-memory handles duplication
It could be considered together with FLINK-32085
was:
As discussed before, we may consider supporting CheckpointStreamFactory for
StateChangeFsUploader:
* need for checkpointId in the current API to resolve the location
*
different settings for materialized/changelog (e.g. timeouts)
*
re-use closeAndGetHandle
*
re-use in-memory handles (.metadata)
*
handle in-memory handles duplication
It could be considered together with FLINK-32085
> Use CheckpointStreamFactory for StateChangeFsUploader
> -----------------------------------------------------
>
> Key: FLINK-34652
> URL: https://issues.apache.org/jira/browse/FLINK-34652
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Hangxiang Yu
> Priority: Major
>
> As discussed before, we may consider supporting CheckpointStreamFactory for
> StateChangeFsUploader:
> * need for checkpointId in the current API to resolve the location
> * different settings for materialized/changelog (e.g. timeouts)
> * re-use closeAndGetHandle
> * re-use in-memory handles (.metadata)
> * handle in-memory handles duplication
> It could be considered together with FLINK-32085
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
