Hi, a user (Hironori Ogibayashi) found another somewhat critical bug: https://issues.apache.org/jira/browse/FLINK-3760
It's an easy fix and I will open a PR momentarily. On Thu, 14 Apr 2016 at 13:17 Ufuk Celebi <u...@apache.org> wrote: > Thanks for your feedback Till and Aljoscha. I will trigger the first RC > today. > > – Ufuk > > On Mon, Apr 11, 2016 at 5:55 PM, Aljoscha Krettek <aljos...@apache.org> > wrote: > > I also found an issue in the RocksDB backend (not introduced by me... > ;-): > > https://issues.apache.org/jira/browse/FLINK-3730 > > > > It's not that critical, however. > > > > On Mon, 11 Apr 2016 at 18:40 Till Rohrmann <trohrm...@apache.org> wrote: > > > >> Given that it's low overhead, then +1 for new bug fix release. If we > find > >> more stuff later on, then we can release another bug fix version. > >> > >> Cheers, > >> Till > >> > >> On Mon, Apr 11, 2016 at 6:32 PM, Ufuk Celebi <u...@apache.org> wrote: > >> > >> > Hey all, > >> > > >> > we recently released Flink 1.0.1, but some fixes did not make it into > >> > the release: > >> > > >> > Major issues reported by users: > >> > - YARN dynamic properties (to be merged to release-1.0), > >> > - POJO key selection, > >> > - WindowOperator.trigger() and watermarks > >> > > >> > Performance improvement: > >> > - Disable WAL in RocksDB > >> > > >> > > >> > Since creating a release is a low overhead async task, I thought about > >> > triggering the new RC soon. > >> > > >> > What do you think? Should we go for it or wait a little more? > >> > > >> > – Ufuk > >> > > >> >
