Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-24 Thread Tzu-Li (Gordon) Tai
Thanks Robert for taking care of this! On March 24, 2017 at 7:24:59 PM, Robert Metzger (rmetz...@apache.org) wrote: Hi Gordon, I didn't see your request for a release manager. I'm volunteering to take this one. Its a little bit easier for me as a PMC member to do the actual release in the e

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-24 Thread Robert Metzger
Hi Gordon, I didn't see your request for a release manager. I'm volunteering to take this one. Its a little bit easier for me as a PMC member to do the actual release in the end. On Fri, Mar 24, 2017 at 7:02 AM, Tzu-Li (Gordon) Tai wrote: > Update for 1.2.1: > > The last fix was just merged! > >

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-23 Thread Tzu-Li (Gordon) Tai
Update for 1.2.1: The last fix was just merged! Since nobody else seems interested in managing 1.2.1, I can also help with this one :) I’ll create the release candidate over the weekend so we can start the testing / voting next Monday. - Gordon On March 22, 2017 at 12:35:25 AM, Tzu-Li (Gordon

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-21 Thread Tzu-Li (Gordon) Tai
Sorry, I missed one other pending issue for Flink 1.2.1: - https://issues.apache.org/jira/browse/FLINK-5972 Disallow shrinking merging windows. This would replace  https://issues.apache.org/jira/browse/FLINK-5713, which was previously listed as a blocker for 1.2.1. Status: PR review pending - htt

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-21 Thread Tzu-Li (Gordon) Tai
Update for Flink 1.2.1: There’s only one PR pending that is LGTM - https://issues.apache.org/jira/browse/FLINK-6084 Fix for Cassandra connector dropping metrics-core dependency. We can proceed to create the release candidate very soon :-) Release 1.1.5 RC1 seems to be in good shape so far, so hop

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-17 Thread Robert Metzger
I don't think that his issue should be a reason to hold back a bugfix release. There are workarounds for the problem you are describing. Once we've fixed it, we can include it into the next upcoming bugfix release. On Fri, Mar 17, 2017 at 4:22 PM, Flavio Pompermaier wrote: > I propose to fix htt

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-17 Thread Flavio Pompermaier
I propose to fix https://issues.apache.org/jira/browse/FLINK-6103 before issue a release On Fri, Mar 17, 2017 at 8:12 AM, Ufuk Celebi wrote: > Cool! Thanks for taking care of this Gordon :-) > > On Fri, Mar 17, 2017 at 7:13 AM, Tzu-Li (Gordon) Tai > wrote: > > Update for 1.1.5: > > The last fix

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-17 Thread Ufuk Celebi
Cool! Thanks for taking care of this Gordon :-) On Fri, Mar 17, 2017 at 7:13 AM, Tzu-Li (Gordon) Tai wrote: > Update for 1.1.5: > The last fixes for 1.1.5 are in! I will create the RC today and start the > vote. > > Cheers, > Gordon > > > On March 17, 2017 at 1:14:53 AM, Robert Metzger (rmetz...

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-16 Thread Tzu-Li (Gordon) Tai
Update for 1.1.5: The last fixes for 1.1.5 are in! I will create the RC today and start the vote. Cheers, Gordon On March 17, 2017 at 1:14:53 AM, Robert Metzger (rmetz...@apache.org) wrote: The cassandra connector is probably not usable in Flink 1.2.0. I would like to include a fix in 1.2.1:

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-16 Thread Robert Metzger
The cassandra connector is probably not usable in Flink 1.2.0. I would like to include a fix in 1.2.1: https://issues.apache.org/jira/browse/FLINK-6084 Please let me know if this fix becomes a blocker for the 1.2.1 release. If so, I can validate the fix myself to speed up things. On Thu, Mar 16,

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-16 Thread Jinkui Shi
@Tzu-li(Fordon)Tai FLINK-5650 is fix by [1]. Chesnay Scheduler push a PR please. [1] https://github.com/zentol/flink/tree/5650_python_test_debug > 在 2017年3月16日,上午3:37,Stephan Ewen 写道: > > Thanks for the update! > > Just merged to

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-15 Thread Stephan Ewen
Thanks for the update! Just merged to 1.2.1 also: [FLINK-5962] [checkpoints] Remove scheduled cancel-task from timer queue to prevent memory leaks The remaining issue list looks good, but I would say that (5) is optional. It is not a critical production bug. On Wed, Mar 15, 2017 at 5:38 PM, Tz

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-15 Thread Tzu-Li (Gordon) Tai
Thanks a lot for the updates so far everyone! From the discussion so far, the below is the still unfixed pending issues for 1.1.5 / 1.2.1 release. Since there’s only one backport for 1.1.5 left, I think having an RC for 1.1.5 near the end of this week / early next week is very promising, as bas

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-15 Thread Jinkui Shi
Can we fix this issue in the 1.2.1: Flink-python tests cost too long time https://issues.apache.org/jira/browse/FLINK-5650 > 在 2017年3月15日,下午6:29,Vladislav Pernin 写道: > > I just tested in in my reproducer. It works. > > 2017-03-15 11:22 GMT+01

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-15 Thread Vladislav Pernin
I just tested in in my reproducer. It works. 2017-03-15 11:22 GMT+01:00 Aljoscha Krettek : > I did in fact just open a PR for > > https://issues.apache.org/jira/browse/FLINK-6001 > > NPE on TumblingEventTimeWindows with ContinuousEventTimeTrigger and > > allowedLateness > > > On Tue, Mar 14, 2017

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-15 Thread Aljoscha Krettek
I did in fact just open a PR for > https://issues.apache.org/jira/browse/FLINK-6001 > NPE on TumblingEventTimeWindows with ContinuousEventTimeTrigger and > allowedLateness On Tue, Mar 14, 2017, at 18:20, Vladislav Pernin wrote: > Hi, > > I would also include the following (not yet resolved) iss

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-14 Thread Vladislav Pernin
Hi, I would also include the following (not yet resolved) issue in the 1.2.1 scope : https://issues.apache.org/jira/browse/FLINK-6001 NPE on TumblingEventTimeWindows with ContinuousEventTimeTrigger and allowedLateness 2017-03-14 17:34 GMT+01:00 Ufuk Celebi : > Big +1 Gordon! > > I think (10) is

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-14 Thread Ufuk Celebi
Big +1 Gordon! I think (10) is very critical to have in 1.2.1. – Ufuk On Tue, Mar 14, 2017 at 3:37 PM, Stefan Richter wrote: > Hi, > > I would suggest to also include in 1.2.1: > > (9) https://issues.apache.org/jira/browse/FLINK-6044 > > Repl

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-14 Thread Stefan Richter
Hi, I would suggest to also include in 1.2.1: (9) https://issues.apache.org/jira/browse/FLINK-6044 Replaces unintentional calls to InputStream#read(…) with the intended and correct InputStream#readFully(…) Status: PR (10) https://issues.apache

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-14 Thread Aljoscha Krettek
Thanks for kicking off the discussion! I have an open PR for - https://issues.apache.org/jira/browse/FLINK-5808: Missing verification for setParallelism and setMaxParallelism - https://issues.apache.org/jira/browse/FLINK-5713: Protect against NPE in WindowOperator window cleanup On Tue, Mar 1

Re: [DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-14 Thread Till Rohrmann
Thanks for kicking off the discussion Tzu-Li. I'd like to add the following issues which have already been merged into the 1.2-release and 1.1-release branch: 1.2.1: (7) https://issues.apache.org/jira/browse/FLINK-5942 Hardens the checkpoint recovery in case of corrupted ZooKeeper data. Corrupted

[DISCUSS] Release Flink 1.1.5 / Flink 1.2.1

2017-03-14 Thread Tzu-Li (Gordon) Tai
Hi all! I would like to start a discussion for the next bugfix release for 1.1.x and 1.2.x. There’s been quite a few critical fixes for bugs in both the releases recently, and I think they deserve a bugfix release soon. Most of the bugs were reported by users. I’m starting the discussion for bo