Re: GenericWriteAheadSink, declined checkpoint for a finished source

2021-12-06 Thread Dawid Wysakowicz
bf82570c86f672ccf2c because Some > tasks of the job have already finished and checkpointing with > finished tasks is not enabled. Failure reason: Not all required > tasks are currently running.* > > > Can anyone advise if this feature is indeed available and wor

Re: GenericWriteAheadSink, declined checkpoint for a finished source

2021-12-06 Thread James Sandys-Lumsdaine
available and working in 1.14.0 and how to correctly enable? Thanks, James. From: Austin Cawley-Edwards Sent: 04 November 2021 18:46 To: James Sandys-Lumsdaine Cc: user@flink.apache.org Subject: Re: GenericWriteAheadSink, declined checkpoint for a finished

Re: GenericWriteAheadSink, declined checkpoint for a finished source

2021-11-04 Thread Caizhi Weng
Hi! Thanks Austin for the answer. I agree that FLIP-147 has solved the problem, just set execution.checkpointing.checkpoints-after-tasks-finish.enabled to true to enable this feature. JDBC sinks solves this problem in a different way. It flushes the sink when closed (see JdbcOutputFormat#close

Re: GenericWriteAheadSink, declined checkpoint for a finished source

2021-11-04 Thread Austin Cawley-Edwards
Hi James, You are correct that since Flink 1.14 [1] (which included FLIP-147 [2]) there is support for checkpointing after some tasks has finished, which sounds like it will solve this use case. You may also want to look at the JDBC sink[3] which also supports batching, as well as some other

GenericWriteAheadSink, declined checkpoint for a finished source

2021-11-03 Thread James Sandys-Lumsdaine
Hello, I have a Flink workflow where I need to upload the output data into a legacy SQL Server database and so I have read the section in the Flink book about data sinks and utilizing the GenericWriteAheadSink base class. I am currently using Flink 1.12.3 although we plan to upgrade to 1.14