Update: FLINK-4618 (https://github.com/apache/flink/pull/2579) had been merged.
There’s another 2 follow-up issues that I also want to include in 1.1.3 for the Kafka connector after review, if others agree: - FLINK-4723 (https://github.com/apache/flink/pull/2580) - FLINK-4727 (https://github.com/apache/flink/pull/2585) (sorry about the duplicate replies earlier, probably a hiccup on my mail client :/) On September 30, 2016 at 2:14:06 PM, Tzu-Li (Gordon) Tai (tzuli...@apache.org) wrote: +1. We should also include FLINK-4618. There isn’t a PR for it yet, but the fix should be fairly quick. Gordon On September 30, 2016 at 1:50:45 AM, Stephan Ewen (se...@apache.org) wrote: +1 for including - FLINK-4311 - FLINK-4702 (https://github.com/apache/flink/pull/2574) - FLINK-4329 (https://github.com/apache/flink/pull/2546) On Thu, Sep 29, 2016 at 3:38 PM, Ufuk Celebi <u...@apache.org> wrote: > +1... Personally, I'm a big fan of frequent bugfix releases :-) > > A user already reported running into the file source problem and > having a very hard time debugging it. This would be good to fix asap. > > – Ufuk > > On Thu, Sep 29, 2016 at 3:20 PM, Fabian Hueske <fhue...@gmail.com> wrote: > > Sounds good to me. > > > > Can we include a fix for FLINK-4311 as well? > > There is a PR [1] which is good to go IMO modulo resetting the updated > > HBase dependency for the 1.1.3 fix. > > For 1.2.0 we should start a discussion about bumping the version. > > > > Cheers, Fabian > > > > [1] https://github.com/apache/flink/pull/2330 > > > > 2016-09-29 15:15 GMT+02:00 Stephan Ewen <se...@apache.org>: > > > >> Hi all! > >> > >> I wanted to bring up having a Flink 1.1.3 bugfix release in the near > >> future. > >> > >> There are some fixed right now in the release-1.1 branch already > (merging > >> windows, optimizer union, ...) and there is a major bug that is > currently > >> fixed in the master: https://issues.apache.org/jira/browse/FLINK-4329 > >> The bug concerns the interplay of file sources and event time. > >> > >> If we decide to head for a 1.1.3, then it makes sense to backport that > fix > >> from master to the release-1.1 branch. > >> > >> What are your thoughts on that? > >> > >> Greetings, > >> Stephan > >> >
