[
https://issues.apache.org/jira/browse/FLINK-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847354#comment-16847354
]
Aljoscha Krettek commented on FLINK-12574:
------------------------------------------
Maybe I understand what you mean now. The part counter is in fact checkpointed,
so if you only ever restore from the latest checkpoint then no data will be
overwritten. If, however, you restore from a checkpoint (or savepoint) that is
not the latest checkpoint (or savepoint) then data will be overwritten. I think
this is true for most (if not all) sink implementations. Is this in fact your
case?
> using sink StreamingFileSink files are overwritten when resuming application
> causing data loss
> ----------------------------------------------------------------------------------------------
>
> Key: FLINK-12574
> URL: https://issues.apache.org/jira/browse/FLINK-12574
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem
> Affects Versions: 1.8.0
> Reporter: yitzchak lieberman
> Priority: Critical
>
> when part files are saved to s3 bucket (with bucket assigner) with simple
> names such as:
> part-0-0 and part-1-2
> restarting or resuming application causes checkpoint id to start from 0 and
> old files will be replaced by new part files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
