[ https://issues.apache.org/jira/browse/FLINK-27910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550583#comment-17550583 ]
David Anderson commented on FLINK-27910: ---------------------------------------- This is super confusing, and there's no reasonable workaround – so I've bumped up the priority to Critical. > FileSink not registered the timer to enforce rolling policy if started from > scratch > ----------------------------------------------------------------------------------- > > Key: FLINK-27910 > URL: https://issues.apache.org/jira/browse/FLINK-27910 > Project: Flink > Issue Type: Bug > Components: Connectors / FileSystem > Affects Versions: 1.15.0, 1.16.0 > Reporter: Yun Gao > Priority: Critical > > The current FileWriter only register the timer in initializeState, which is > now only called on restoring. Thus if the job is started from scratch, the > timer would fail to be registered and cause the rolling policy not work. -- This message was sent by Atlassian Jira (v8.20.7#820007)