[DISCUSS] Release Flink 1.0.2

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Release Flink 1.0.2

Ufuk Celebi-2
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
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Release Flink 1.0.2

Till Rohrmann
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 <[hidden email]> 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
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Release Flink 1.0.2

Aljoscha Krettek-2
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 <[hidden email]> 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 <[hidden email]> 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
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Release Flink 1.0.2

Ufuk Celebi-2
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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
>> >
>>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Release Flink 1.0.2

Aljoscha Krettek-2
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 <[hidden email]> 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 <[hidden email]>
> 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 <[hidden email]> 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 <[hidden email]> 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
> >> >
> >>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Release Flink 1.0.2

Ufuk Celebi-2
Just started the vote but let's include it. No biggie. I will re-run the
script later today.

On Thursday, 14 April 2016, Aljoscha Krettek <[hidden email]> wrote:

> 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 <[hidden email] <javascript:;>>
> 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 <[hidden email]
> <javascript:;>>
> > 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 <[hidden email]
> <javascript:;>> 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 <[hidden email]
> <javascript:;>> 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
> > >> >
> > >>
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Release Flink 1.0.2

Aljoscha Krettek-2
Thanks, sorry for the inconvenience :-O

On Thu, 14 Apr 2016 at 16:11 Ufuk Celebi <[hidden email]> wrote:

> Just started the vote but let's include it. No biggie. I will re-run the
> script later today.
>
> On Thursday, 14 April 2016, Aljoscha Krettek <[hidden email]> wrote:
>
> > 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 <[hidden email] <javascript:;>>
> > 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 <[hidden email]
> > <javascript:;>>
> > > 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 <[hidden email]
> > <javascript:;>> 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 <[hidden email]
> > <javascript:;>> 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
> > > >> >
> > > >>
> > >
> >
>