Return-Path: <user-return-14357-archive-asf-public=cust-asf.ponee.io@flink.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 4E500200CD3
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri, 28 Jul 2017 16:03:58 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 4CA6C16CDA4; Fri, 28 Jul 2017 14:03:58 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 9202D16CDA0
	for <archive-asf-public@cust-asf.ponee.io>; Fri, 28 Jul 2017 16:03:57 +0200 (CEST)
Received: (qmail 21036 invoked by uid 500); 28 Jul 2017 14:03:51 -0000
Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@flink.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@flink.apache.org>
List-Post: <mailto:user@flink.apache.org>
List-Id: <user.flink.apache.org>
Delivered-To: mailing list user@flink.apache.org
Received: (qmail 21019 invoked by uid 99); 28 Jul 2017 14:03:51 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jul 2017 14:03:51 +0000
Received: from mail-pg0-f47.google.com (mail-pg0-f47.google.com [74.125.83.47])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C5FB81A0019;
	Fri, 28 Jul 2017 14:03:50 +0000 (UTC)
Received: by mail-pg0-f47.google.com with SMTP id 125so111714051pgi.3;
        Fri, 28 Jul 2017 07:03:49 -0700 (PDT)
X-Gm-Message-State: AIVw113lkhVraXzPDZ3WsNWGtqh2BHTMIpKjQPXxZWcUgzm3t7HUVbZ9
	Esf+17R+hu/NAWFSMGkPYZt6J5sueg==
X-Received: by 10.98.155.90 with SMTP id r87mr7644049pfd.56.1501250628469;
 Fri, 28 Jul 2017 07:03:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.169.11 with HTTP; Fri, 28 Jul 2017 07:03:33 -0700 (PDT)
In-Reply-To: <CANC1h_tcDLKjZni2H3bzZgZwdYVjttdhzJ-2ES9x2LwYEDfo0g@mail.gmail.com>
References: <CANC1h_tcDLKjZni2H3bzZgZwdYVjttdhzJ-2ES9x2LwYEDfo0g@mail.gmail.com>
From: Stephan Ewen <sewen@apache.org>
Date: Fri, 28 Jul 2017 16:03:33 +0200
X-Gmail-Original-Message-ID: <CANC1h_tPKiLBP46yX4tK_uw2sNmVvm3THh-MX4qryBuHQimZag@mail.gmail.com>
Message-ID: <CANC1h_tPKiLBP46yX4tK_uw2sNmVvm3THh-MX4qryBuHQimZag@mail.gmail.com>
Subject: Re: [POLL] Dropping savepoint format compatibility for 1.1.x in the
 Flink 1.4.0 release
To: user <user@flink.apache.org>
Cc: "dev@flink.apache.org" <dev@flink.apache.org>
Content-Type: multipart/alternative; boundary="94eb2c1163966dcb4105556126d5"
archived-at: Fri, 28 Jul 2017 14:03:58 -0000

--94eb2c1163966dcb4105556126d5
Content-Type: text/plain; charset="UTF-8"

Seems like no one raised a concern so far about dropping the savepoint
format compatibility for 1.1 in 1.4.

Leaving this thread open for some more days, but from the sentiment, it
seems like we should go ahead?

On Wed, Jul 12, 2017 at 4:43 PM, Stephan Ewen <sewen@apache.org> wrote:

> Hi users!
>
> Flink currently maintains backwards compatibility for savepoint formats,
> which means that savepoints taken with Flink version 1.1.x and 1.2.x can be
> resumed in Flink 1.3.x
>
> We are discussing how many versions back to support. The proposition is
> the following:
>
> *   Suggestion: Flink 1.4.0 will be able to resume savepoints taken with
> version 1.3.x and 1.2.x, but not savepoints from version 1.1.x and 1.0.x*
>
>
> The reason for that is that there is a lot of code mapping between the
> completely different legacy format (1.1.x, not re-scalable) and the
> key-group-oriented format (1.2.x onwards, re-scalable). It would greatly
> help the development of state and checkpointing features to drop that old
> code.
>
> Please let us know if you have concerns about that.
>
> Best,
> Stephan
>
>

--94eb2c1163966dcb4105556126d5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Seems like no one raised a concern so far about dropping t=
he savepoint format compatibility for 1.1=C2=A0in 1.4.<div><br></div><div>L=
eaving this thread open for some more days, but from the sentiment, it seem=
s like we should go ahead?</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Wed, Jul 12, 2017 at 4:43 PM, Stephan Ewen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:sewen@apache.org" target=3D"_blank">sewen@apach=
e.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"l=
tr">Hi users!<div><br></div><div>Flink currently maintains backwards compat=
ibility for savepoint formats, which means that savepoints taken with Flink=
 version 1.1.x and 1.2.x can be resumed in Flink 1.3.x</div><div><br></div>=
<div>We are discussing how many versions back to support. The proposition i=
s the following:</div><div><br></div><div><b>=C2=A0 =C2=A0Suggestion:=C2=A0=
Flink 1.4.0 will be able to resume savepoints taken with version 1.3.x and =
1.2.x, but not savepoints from version 1.1.x and 1.0.x</b></div><div><br></=
div><div><br></div><div>The reason for that is that there is a lot of code =
mapping between the completely different legacy format (1.1.x, not re-scala=
ble) and the key-group-oriented format (1.2.x onwards, re-scalable). It wou=
ld greatly help the development of state and checkpointing features to drop=
 that old code.</div><div><br></div><div>Please let us know if you have con=
cerns about that.</div><div><br></div><div>Best,</div><div>Stephan</div><di=
v><br></div></div>
</blockquote></div><br></div></div>

--94eb2c1163966dcb4105556126d5--