[ 
https://issues.apache.org/jira/browse/FLINK-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mario Georgiev updated FLINK-12172:
-----------------------------------
    Description: 
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.

  was:
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. 


> Flink fails to close pending BucketingSink
> ------------------------------------------
>
>                 Key: FLINK-12172
>                 URL: https://issues.apache.org/jira/browse/FLINK-12172
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 1.7.2
>            Reporter:  Mario Georgiev
>            Priority: Major
>
> 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
(v7.6.3#76005)

Reply via email to