://search-hadoop.com/m/Flink/VkLeQ0dXIf1SkHpY?subj=Re+Does+job+restart+resume+from+last+known+internal+checkpoint+
> On Wed, Jul 19, 2017 at 9:02 AM, Moiz Jinia wrote:
> Yup! Thanks.
>
> Moiz
>
> —
> sent from phone
>
> On 19-Jul-2017, at 9:21 PM, Aljoscha Krettek [vi
Yup! Thanks.
Moiz
—
sent from phone
On 19-Jul-2017, at 9:21 PM, Aljoscha Krettek [via Apache Flink User Mailing
List archive.] wrote:
This was now answered in your other Thread, right?
Best,
Aljoscha
>> On 18. Jul 2017, at 11:37, Moiz Jinia <[hidden email]> wrote:
>>
&
Below is a plan for downtime-free upgrade of a Flink job. The downstream
consumer of the Flink job is duplicate proof.
Scenario 1 -
1. Start Flink job A with consumer group G1 (12 slot job)
2. While job A is running, take a savepoint AS.
3. Start newer version of Flink job A' from savepoint AS wit
Aljoscha Krettek wrote
> Hi,
> zero-downtime updates are currently not supported. What is supported in
> Flink right now is a savepoint-shutdown-restore cycle. With this, you
> first
> draw a savepoint (which is essentially a checkpoint with some meta data),
> then you cancel your job, then you do
It'll definitely have a where clause. Just forgot to include it in the example.
Just meant to focus on the within clause.
Am on 1.3 - expect it'll be fixed by the time stable is out?
Thanks!
Moiz
—
sent from phone
On 04-May-2017, at 8:12 PM, Kostas Kloudas wrote:
Hi Moiz,
You are on Flink
Hey David,
Did that work for you? If yes could you share an example. I have a similar
use case - need to get notified of an event NOT occurring within a specified
time window.
Thanks much!
Moiz
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.co
