Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: Aljoscha Krettek <aljoscha@apache.org>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_A5B8B286-6392-4D90-BA21-2E95502CA65E"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [DISCUSS] Release Apache Flink 1.3.1
Date: Tue, 13 Jun 2017 11:21:59 +0200
References: <CAGr9p8CQGQVNfOA7Od_yY1z6TCHpWMHT-TSkSjM9fLuVZsq21w@mail.gmail.com>
 <2138045.JOYR12dcUs@nico-work> <etPan.59366ebd.35aa019e.1625d@apache.org>
 <CAGr9p8AdDq-SU-jqODuc+yTg=2BxLsM3A8RUUXtNo+Xqbbmx5g@mail.gmail.com>
 <3F4AA781-75B6-4B0B-94FE-C17336DE77F5@apache.org>
 <CAC27z=PE7RWKkzOzP8QETP1jPMYwXuxK=uu1xCe_NJh8t+x3+Q@mail.gmail.com>
 <0F2B9B3E-A802-49FE-BA8F-4388F62FAB1D@apache.org>
 <etPan.593f802f.7292cd11.110@apache.org>
 <CAJSjTKxtVcdYP2p7qoiVTqVsaO2Vhashya96tNhnrD=uM3x4Mw@mail.gmail.com>
 <f54b9b20-9eb1-82c9-e36f-3750b5df9ba3@apache.org>
To: dev@flink.apache.org
In-Reply-To: <f54b9b20-9eb1-82c9-e36f-3750b5df9ba3@apache.org>
Message-Id: <AA6342EA-7565-41EA-9553-4D689A811209@apache.org>
archived-at: Tue, 13 Jun 2017 09:22:07 -0000

--Apple-Mail=_A5B8B286-6392-4D90-BA21-2E95502CA65E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

A quick Jira search reveals one blocker: =
https://issues.apache.org/jira/browse/FLINK-6685?filter=3D12334772&jql=3Dp=
roject%20%3D%20FLINK%20AND%20priority%20%3D%20Blocker%20AND%20resolution%2=
0%3D%20Unresolved%20AND%20affectedVersion%20%3D%201.3.0 =
<https://issues.apache.org/jira/browse/FLINK-6685?filter=3D12334772&jql=3D=
project%20=3D%20FLINK%20AND%20priority%20=3D%20Blocker%20AND%20resolution%=
20=3D%20Unresolved%20AND%20affectedVersion%20=3D%201.3.0>

> On 13. Jun 2017, at 10:12, Chesnay Schepler <chesnay@apache.org> =
wrote:
>=20
> I would like to include FLINK-6898 and FLINK-6900 in 1.3.1.
>=20
> They are related to the metric system, and limit the size of =
individual metric name components
> as the default window operator names are so long they were causing =
issues with file-system based
> storages because the components exceeded 255 characters.
>=20
> They both have open PRs and change 1 and 3 lines respectively, so it's =
very fast to review.
>=20
> On 13.06.2017 09:33, jincheng sun wrote:
>> Hi Robert,
>>  =46rom user mail-list I find 2 bugs as follows:
>>=20
>>  https://issues.apache.org/jira/browse/FLINK-6886
>>  https://issues.apache.org/jira/browse/FLINK-6896
>>=20
>> I'm not sure if they are as the release blocker. But I think is =
better to
>> merged those two PR. into 1.3.1 release.
>> What do you think? @Fabian, @Timo, @Robert
>>=20
>> Best,
>> SunJincheng
>>=20
>>=20
>> 2017-06-13 14:03 GMT+08:00 Tzu-Li (Gordon) Tai <tzulitai@apache.org>:
>>=20
>>> I=E2=80=99ve just merged the last blockers for 1.3.1. IMO, the =
release process for
>>> 1.3.1 is ready for kick off.
>>>=20
>>>=20
>>> On 8 June 2017 at 10:32:47 AM, Aljoscha Krettek =
(aljoscha@apache.org)
>>> wrote:
>>>=20
>>> Yes, there is a workaround, as mentioned in the other thread:
>>> https://lists.apache.org/thread.html/eb7e256146fbe069a4210e1690fac5
>>> d3453208fab61515ab1a2f6bf7@%3Cuser.flink.apache.org%3E <
>>> https://lists.apache.org/thread.html/eb7e256146fbe069a4210e1690fac5
>>> d3453208fab61515ab1a2f6bf7@%3Cuser.flink.apache.org%3E>. It=E2=80=99s =
just a bit
>>> cumbersome but I agree that it=E2=80=99s not a blocker now.
>>>=20
>>> Best,
>>> Aljoscha
>>>> On 8. Jun 2017, at 09:47, Till Rohrmann <trohrmann@apache.org> =
wrote:
>>>>=20
>>>> There should be an easy work-around for this problem. Start a =
standalone
>>>> cluster and run the queries against this cluster. But I also see =
that it
>>>> might be annoying for users who used to do it differently. The =
basic
>>>> question here should be whether we want the users to use the
>>>> LocalFlinkMiniCluster in a remote setting (running queries against =
it
>>> from
>>>> a different process).
>>>>=20
>>>> Cheers,
>>>> Till
>>>>=20
>>>> On Wed, Jun 7, 2017 at 4:59 PM, Aljoscha Krettek =
<aljoscha@apache.org>
>>>> wrote:
>>>>=20
>>>>> I would also like to raise another potential blocker: it=E2=80=99s =
currently not
>>>>> easily possible for users to start a job in local mode in the IDE =
and to
>>>>> then interact with that cluster, say for experimenting with =
queryable
>>>>> state. At least one user walked into this problem already with the =
1.3.0
>>>>> RC: =
https://lists.apache.org/thread.html/eb7e256146fbe069a4210e1690fac5
>>>>> d3453208fab61515ab1a2f6bf7@%3Cuser.flink.apache.org%3E <
>>>>> =
https://lists.apache.org/thread.html/eb7e256146fbe069a4210e1690fac5
>>>>> d3453208fab61515ab1a2f6bf7@%3Cuser.flink.apache.org%3E>
>>>>>=20
>>>>> The reasons I have so far analysed are:
>>>>> * the local flink cluster starts with HAServices that don=E2=80=99t =
allow
>>>>> external querying, by default. (Broadly spoken)
>>>>> * the queryable state server is not started in the local flink =
mini
>>>>> cluster anymore and it cannot be configured to do so easily
>>>>>=20
>>>>> What do you think?
>>>>>=20
>>>>> Best,
>>>>> Aljoscha
>>>>>> On 7. Jun 2017, at 11:54, Robert Metzger <rmetzger@apache.org> =
wrote:
>>>>>>=20
>>>>>> =46rom the list [1], not many of the JIRAs have been fixed.
>>>>>> I think it would be nice to put the RC for 1.3.1 out this week, =
given
>>>>> that
>>>>>> multiple users have complained about some issues in the 1.3.0 =
release.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> [1]
>>>>>> https://issues.apache.org/jira/issues/?jql=3Dlabels%20%3D%
>>>>> 20flink-rel-1.3.1-blockers
>>>>>> On Tue, Jun 6, 2017 at 10:58 AM, Tzu-Li (Gordon) Tai <
>>>>> tzulitai@apache.org>
>>>>>> wrote:
>>>>>>=20
>>>>>>> After an offline discussion with Till, we decided to not include
>>>>>>> FLINK-6763 and FLINK-6764 as blockers for 1.3.1, and only merge =
them
>>> for
>>>>>>> 1.4.0 since they change serialization formats for checkpoints.
>>>>>>>=20
>>>>>>> In turn, I=E2=80=99ve included https://issues.apache.org/
>>> jira/browse/FLINK-6804
>>>>> as
>>>>>>> a 1.3.1 blocker.
>>>>>>>=20
>>>>>>>=20
>>>>>>> On 2 June 2017 at 5:27:18 PM, Nico Kruber =
(nico@data-artisans.com)
>>>>> wrote:
>>>>>>> while fixing build issues - what about FLINK-6654?
>>>>>>>=20
>>>>>>> On Friday, 2 June 2017 11:05:34 CEST Robert Metzger wrote:
>>>>>>>> Hi devs,
>>>>>>>>=20
>>>>>>>> I would like to release Apache Flink 1.3.1 with the following =
fixes:
>>>>>>>>=20
>>>>>>>> - FLINK-6812 Elasticsearch 5 release artifacts not published to =
Maven
>>>>>>>> central
>>>>>>>> - FLINK-6783 Wrongly extracted TypeInformations for
>>>>>>>> WindowedStream::aggregate
>>>>>>>> - FLINK-6780 ExternalTableSource should add time attributes in =
the
>>> row
>>>>>>> type
>>>>>>>> - FLINK-6775 StateDescriptor cannot be shared by multiple =
subtasks
>>>>>>>> - FLINK-6763 Inefficient PojoSerializerConfigSnapshot =
serialization
>>>>>>> format
>>>>>>>> - FLINK-6764 Deduplicate stateless TypeSerializers when =
serializing
>>>>>>>> composite TypeSerializers
>>>>>>>>=20
>>>>>>>> Is there anything else that we need to wait for before we vote =
on the
>>>>>>> first
>>>>>>>> RC?
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Regards,
>>>>>>>> Robert
>>>>>>>=20
>>>>>=20
>>>=20
>=20


--Apple-Mail=_A5B8B286-6392-4D90-BA21-2E95502CA65E--