[
https://issues.apache.org/jira/browse/FLINK-8539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-8539.
---------------------------------
Resolution: Fixed
Fixed as of d85a62db13a1d90159e7e8f924c8006febad552b
- f9dd19b584fca5932594392b0afc9f1d0eec7f1a
- f577d2603fb0432fa7a15d54ee25f481bde95d95
- d85a62db13a1d90159e7e8f924c8006febad552b
> Introduce "CompletedCheckpointStorageLocation" to explicitly handle disposal
> of checkpoint storage locations
> ------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-8539
> URL: https://issues.apache.org/jira/browse/FLINK-8539
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Fix For: 1.5.0
>
>
> The storage location of completed checkpoints misses a proper representation.
> Because of that, there is no place that can handle the deletion of a
> checkpoint directory, or the dropping of a checkpoint specific table.
> Current workaround for file systems is, for example, that every file disposal
> checks if the parent directory is now empty, and deletes it if that is the
> case. That is not only inefficient, but prohibitively expensive on some
> systems, like Amazon S3.
> Properly representing the storage location for completed checkpoints allows
> us to add a disposal call for that location.
> That {{CompletedCheckpointStorageLocation}} can also be used to capture
> "external pointers", metadata, and even allow us to use custom serialization
> and deserialization of the metadata in the future, making the abstraction
> more extensible by allowing users to introduce new types of state handles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
