[
https://issues.apache.org/jira/browse/FLINK-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12172:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Flink fails to close pending BucketingSink
> ------------------------------------------
>
> Key: FLINK-12172
> URL: https://issues.apache.org/jira/browse/FLINK-12172
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem
> Affects Versions: 1.7.2
> Reporter: Mario Georgiev
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Hello,
> The problem is if you have a BucketingSink, the following case may occur :
> Let's say you have a 2019-04-12–12 bucket created with several files inside
> which are pending/finished
> You create a savepoint and shut down the job
> After an hour for instance you start the job from the savepoint and a new
> bucket is created, 2019-04-16 for instance.
> The problem is that the .pending ones from the old buckets seem to never be
> moved to finished state if there is a new hourly bucket created.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
