Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Robert Metzger]

Hi all,

I've opened a pull request for the release announcement. I'm looking
forward to your review & feedback:
https://github.com/apache/flink-web/pull/244

On Fri, Aug 9, 2019 at 6:27 PM Tzu-Li (Gordon) Tai 
wrote:

> Hi,
>
> Update: voting on RC2 for Apache Flink 1.9.0 has started:
>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Apache-Flink-Release-1-9-0-release-candidate-2-td31542.html
>
> Cheers,
> Gordon
>
> On Thu, Aug 8, 2019 at 5:40 PM Fabian Hueske  wrote:
>
> > OK, let's stop the discussion about the playground in the release 1.9
> > thread.
> > I've started a new thread on dev@f.a.o to continue the discussion [1].
> >
> > Best, Fabian
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/4f54c0b4162e3db8626afdca5c354050282282d3cc229d01f2d8ca3e@%3Cdev.flink.apache.org%3E
> >
> > Am Do., 8. Aug. 2019 um 15:23 Uhr schrieb Konstantin Knauf <
> > konstan...@ververica.com>:
> >
> > > Hi Till,
> > >
> > > we will try to find another way to make the playground available for
> > users
> > > soon. The discussion of and how to split up the Flink Repository
> started
> > > only after we discussed the playground and flink-playgrounds
> > repositories.
> > > I think, this is the reason we went this way, not necessarily
> > convenience.
> > >
> > > Cheers,
> > >
> > > Konstantin
> > >
> > > On Thu, Aug 8, 2019 at 2:25 PM Till Rohrmann 
> > wrote:
> > >
> > > > Just as a short addendum, there are also benefits of having the
> > > > ClickEventCount job not being part of the Flink repository. Assume
> > there
> > > is
> > > > a bug in the job, then you would have to wait for the next Flink
> > release
> > > to
> > > > fix it.
> > > >
> > > > On Thu, Aug 8, 2019 at 2:24 PM Till Rohrmann 
> > > wrote:
> > > >
> > > > > I see that keeping the playground job in the Flink repository has a
> > > > couple
> > > > > of advantages, among other things that it's easier to keep up to
> > date.
> > > > > However, in particular in the light of the potential repository
> split
> > > > where
> > > > > we want to separate connectors from Flink core, it seems very
> > > problematic
> > > > > to put the ClickEventCount which depends on Flink's Kafka connector
> > in
> > > > > Flink's distribution. To me it seems that this was the path of
> least
> > > > > resistance but I'm not sure whether it stays like this. I think it
> > > would
> > > > > have been cleaner to separate the playground project from Flink
> core.
> > > > >
> > > > > Cheers,
> > > > > Till
> > > > >
> > > > > On Thu, Aug 8, 2019 at 1:28 PM Konstantin Knauf <
> > > > konstan...@ververica.com>
> > > > > wrote:
> > > > >
> > > > >> Hi Till,
> > > > >>
> > > > >> as Fabian said, we considered the option you mentioned, but in the
> > end
> > > > >> decided that not maintaining a separate images has more
> advantages.
> > > > >>
> > > > >> In the context of FLIP-42 we are also revisiting the examples in
> > > general
> > > > >> and want to clean these up a bit. So, for what it's worth, there
> > will
> > > be
> > > > >> an
> > > > >> opportunity for revisiting this topic soon.
> > > > >>
> > > > >> Best,
> > > > >>
> > > > >> Konstantin
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske 
> > > > wrote:
> > > > >>
> > > > >> > The motivation for including the job as an example is to not
> have
> > to
> > > > >> > maintain a separate Docker image.
> > > > >> > We would like to use the regular Flink 1.9 image for the
> > playground
> > > > and
> > > > >> > avoid to maintain an image that is slightly different from the
> > > regular
> > > > >> 1.9
> > > > >> > image.
> > > > >> >
> > > > >> > Maintaining the job in a different repository or somewhere else
> > > would
> > > > >> mean,
> > > > >> > that we need to have a proper release cycle for it as well.
> > > > >> > Having it among the other examples means it's included in the
> > > regular
> > > > >> > release.
> > > > >> >
> > > > >> > Best, Fabian
> > > > >> >
> > > > >> >
> > > > >> > Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
> > > > >> > trohrm...@apache.org>:
> > > > >> >
> > > > >> > > Before backporting the playground PR to the release-1.9, I'd
> > like
> > > to
> > > > >> > > understand why the ClickEventCount job needs to be part of the
> > > Flink
> > > > >> > > distribution. Looking at the example, it seems to only work in
> > > > >> > combination
> > > > >> > > with a Kafka cluster. Since it is not self-contained, it does
> > not
> > > > add
> > > > >> > much
> > > > >> > > value for a user who does not want to use the playgrounds.
> > > Moreover,
> > > > >> we
> > > > >> > > already have the StateMachineExample job which can be used to
> > read
> > > > >> from
> > > > >> > > Kafka if a Kafka cluster is available. So my question would be
> > why
> > > > >> don't
> > > > >> > we
> > > > >> > > include the example job in the docker images for the
> playground?
> > > > This
> > > > >> > would
> > > > >> > > be in my opinion a be

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

Hi,

Update: voting on RC2 for Apache Flink 1.9.0 has started:
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Apache-Flink-Release-1-9-0-release-candidate-2-td31542.html

Cheers,
Gordon

On Thu, Aug 8, 2019 at 5:40 PM Fabian Hueske  wrote:

> OK, let's stop the discussion about the playground in the release 1.9
> thread.
> I've started a new thread on dev@f.a.o to continue the discussion [1].
>
> Best, Fabian
>
> [1]
>
> https://lists.apache.org/thread.html/4f54c0b4162e3db8626afdca5c354050282282d3cc229d01f2d8ca3e@%3Cdev.flink.apache.org%3E
>
> Am Do., 8. Aug. 2019 um 15:23 Uhr schrieb Konstantin Knauf <
> konstan...@ververica.com>:
>
> > Hi Till,
> >
> > we will try to find another way to make the playground available for
> users
> > soon. The discussion of and how to split up the Flink Repository started
> > only after we discussed the playground and flink-playgrounds
> repositories.
> > I think, this is the reason we went this way, not necessarily
> convenience.
> >
> > Cheers,
> >
> > Konstantin
> >
> > On Thu, Aug 8, 2019 at 2:25 PM Till Rohrmann 
> wrote:
> >
> > > Just as a short addendum, there are also benefits of having the
> > > ClickEventCount job not being part of the Flink repository. Assume
> there
> > is
> > > a bug in the job, then you would have to wait for the next Flink
> release
> > to
> > > fix it.
> > >
> > > On Thu, Aug 8, 2019 at 2:24 PM Till Rohrmann 
> > wrote:
> > >
> > > > I see that keeping the playground job in the Flink repository has a
> > > couple
> > > > of advantages, among other things that it's easier to keep up to
> date.
> > > > However, in particular in the light of the potential repository split
> > > where
> > > > we want to separate connectors from Flink core, it seems very
> > problematic
> > > > to put the ClickEventCount which depends on Flink's Kafka connector
> in
> > > > Flink's distribution. To me it seems that this was the path of least
> > > > resistance but I'm not sure whether it stays like this. I think it
> > would
> > > > have been cleaner to separate the playground project from Flink core.
> > > >
> > > > Cheers,
> > > > Till
> > > >
> > > > On Thu, Aug 8, 2019 at 1:28 PM Konstantin Knauf <
> > > konstan...@ververica.com>
> > > > wrote:
> > > >
> > > >> Hi Till,
> > > >>
> > > >> as Fabian said, we considered the option you mentioned, but in the
> end
> > > >> decided that not maintaining a separate images has more advantages.
> > > >>
> > > >> In the context of FLIP-42 we are also revisiting the examples in
> > general
> > > >> and want to clean these up a bit. So, for what it's worth, there
> will
> > be
> > > >> an
> > > >> opportunity for revisiting this topic soon.
> > > >>
> > > >> Best,
> > > >>
> > > >> Konstantin
> > > >>
> > > >>
> > > >>
> > > >> On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske 
> > > wrote:
> > > >>
> > > >> > The motivation for including the job as an example is to not have
> to
> > > >> > maintain a separate Docker image.
> > > >> > We would like to use the regular Flink 1.9 image for the
> playground
> > > and
> > > >> > avoid to maintain an image that is slightly different from the
> > regular
> > > >> 1.9
> > > >> > image.
> > > >> >
> > > >> > Maintaining the job in a different repository or somewhere else
> > would
> > > >> mean,
> > > >> > that we need to have a proper release cycle for it as well.
> > > >> > Having it among the other examples means it's included in the
> > regular
> > > >> > release.
> > > >> >
> > > >> > Best, Fabian
> > > >> >
> > > >> >
> > > >> > Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
> > > >> > trohrm...@apache.org>:
> > > >> >
> > > >> > > Before backporting the playground PR to the release-1.9, I'd
> like
> > to
> > > >> > > understand why the ClickEventCount job needs to be part of the
> > Flink
> > > >> > > distribution. Looking at the example, it seems to only work in
> > > >> > combination
> > > >> > > with a Kafka cluster. Since it is not self-contained, it does
> not
> > > add
> > > >> > much
> > > >> > > value for a user who does not want to use the playgrounds.
> > Moreover,
> > > >> we
> > > >> > > already have the StateMachineExample job which can be used to
> read
> > > >> from
> > > >> > > Kafka if a Kafka cluster is available. So my question would be
> why
> > > >> don't
> > > >> > we
> > > >> > > include the example job in the docker images for the playground?
> > > This
> > > >> > would
> > > >> > > be in my opinion a better separation of concerns.
> > > >> > >
> > > >> > > I've cross posted my question on the original PR as well.
> > > >> > >
> > > >> > > Cheers,
> > > >> > > Till
> > > >> > >
> > > >> > > On Thu, Aug 8, 2019 at 9:23 AM Kurt Young 
> > wrote:
> > > >> > >
> > > >> > > > +1 to include this in 1.9.0, adding some examples doesn't look
> > > like
> > > >> new
> > > >> > > > feature to me.
> > > >> > > > BTW, I am also trying this tutorial based on release-1.9
> branch,
> > > but
> > > >> > > > blocked by:
> > > >> > > >
> >

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Fabian Hueske]

OK, let's stop the discussion about the playground in the release 1.9
thread.
I've started a new thread on dev@f.a.o to continue the discussion [1].

Best, Fabian

[1]
https://lists.apache.org/thread.html/4f54c0b4162e3db8626afdca5c354050282282d3cc229d01f2d8ca3e@%3Cdev.flink.apache.org%3E

Am Do., 8. Aug. 2019 um 15:23 Uhr schrieb Konstantin Knauf <
konstan...@ververica.com>:

> Hi Till,
>
> we will try to find another way to make the playground available for users
> soon. The discussion of and how to split up the Flink Repository started
> only after we discussed the playground and flink-playgrounds repositories.
> I think, this is the reason we went this way, not necessarily convenience.
>
> Cheers,
>
> Konstantin
>
> On Thu, Aug 8, 2019 at 2:25 PM Till Rohrmann  wrote:
>
> > Just as a short addendum, there are also benefits of having the
> > ClickEventCount job not being part of the Flink repository. Assume there
> is
> > a bug in the job, then you would have to wait for the next Flink release
> to
> > fix it.
> >
> > On Thu, Aug 8, 2019 at 2:24 PM Till Rohrmann 
> wrote:
> >
> > > I see that keeping the playground job in the Flink repository has a
> > couple
> > > of advantages, among other things that it's easier to keep up to date.
> > > However, in particular in the light of the potential repository split
> > where
> > > we want to separate connectors from Flink core, it seems very
> problematic
> > > to put the ClickEventCount which depends on Flink's Kafka connector in
> > > Flink's distribution. To me it seems that this was the path of least
> > > resistance but I'm not sure whether it stays like this. I think it
> would
> > > have been cleaner to separate the playground project from Flink core.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Thu, Aug 8, 2019 at 1:28 PM Konstantin Knauf <
> > konstan...@ververica.com>
> > > wrote:
> > >
> > >> Hi Till,
> > >>
> > >> as Fabian said, we considered the option you mentioned, but in the end
> > >> decided that not maintaining a separate images has more advantages.
> > >>
> > >> In the context of FLIP-42 we are also revisiting the examples in
> general
> > >> and want to clean these up a bit. So, for what it's worth, there will
> be
> > >> an
> > >> opportunity for revisiting this topic soon.
> > >>
> > >> Best,
> > >>
> > >> Konstantin
> > >>
> > >>
> > >>
> > >> On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske 
> > wrote:
> > >>
> > >> > The motivation for including the job as an example is to not have to
> > >> > maintain a separate Docker image.
> > >> > We would like to use the regular Flink 1.9 image for the playground
> > and
> > >> > avoid to maintain an image that is slightly different from the
> regular
> > >> 1.9
> > >> > image.
> > >> >
> > >> > Maintaining the job in a different repository or somewhere else
> would
> > >> mean,
> > >> > that we need to have a proper release cycle for it as well.
> > >> > Having it among the other examples means it's included in the
> regular
> > >> > release.
> > >> >
> > >> > Best, Fabian
> > >> >
> > >> >
> > >> > Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
> > >> > trohrm...@apache.org>:
> > >> >
> > >> > > Before backporting the playground PR to the release-1.9, I'd like
> to
> > >> > > understand why the ClickEventCount job needs to be part of the
> Flink
> > >> > > distribution. Looking at the example, it seems to only work in
> > >> > combination
> > >> > > with a Kafka cluster. Since it is not self-contained, it does not
> > add
> > >> > much
> > >> > > value for a user who does not want to use the playgrounds.
> Moreover,
> > >> we
> > >> > > already have the StateMachineExample job which can be used to read
> > >> from
> > >> > > Kafka if a Kafka cluster is available. So my question would be why
> > >> don't
> > >> > we
> > >> > > include the example job in the docker images for the playground?
> > This
> > >> > would
> > >> > > be in my opinion a better separation of concerns.
> > >> > >
> > >> > > I've cross posted my question on the original PR as well.
> > >> > >
> > >> > > Cheers,
> > >> > > Till
> > >> > >
> > >> > > On Thu, Aug 8, 2019 at 9:23 AM Kurt Young 
> wrote:
> > >> > >
> > >> > > > +1 to include this in 1.9.0, adding some examples doesn't look
> > like
> > >> new
> > >> > > > feature to me.
> > >> > > > BTW, I am also trying this tutorial based on release-1.9 branch,
> > but
> > >> > > > blocked by:
> > >> > > >
> > >> > > > git clone --branch release-1.10-SNAPSHOT
> > >> > > > g...@github.com:apache/flink-playgrounds.git
> > >> > > >
> > >> > > > Neither 1.10 nor 1.9 exists in flink-playground yet.
> > >> > > >
> > >> > > > Best,
> > >> > > > Kurt
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske  >
> > >> > wrote:
> > >> > > >
> > >> > > > > Hi,
> > >> > > > > I worked with Konstantin and reviewed the PR.
> > >> > > > > I think the playground is a great way to get started with
> Flink
> > >> and
> > >> > > > explore
> > >> > > > > it's r

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Konstantin Knauf]

Hi Till,

we will try to find another way to make the playground available for users
soon. The discussion of and how to split up the Flink Repository started
only after we discussed the playground and flink-playgrounds repositories.
I think, this is the reason we went this way, not necessarily convenience.

Cheers,

Konstantin

On Thu, Aug 8, 2019 at 2:25 PM Till Rohrmann  wrote:

> Just as a short addendum, there are also benefits of having the
> ClickEventCount job not being part of the Flink repository. Assume there is
> a bug in the job, then you would have to wait for the next Flink release to
> fix it.
>
> On Thu, Aug 8, 2019 at 2:24 PM Till Rohrmann  wrote:
>
> > I see that keeping the playground job in the Flink repository has a
> couple
> > of advantages, among other things that it's easier to keep up to date.
> > However, in particular in the light of the potential repository split
> where
> > we want to separate connectors from Flink core, it seems very problematic
> > to put the ClickEventCount which depends on Flink's Kafka connector in
> > Flink's distribution. To me it seems that this was the path of least
> > resistance but I'm not sure whether it stays like this. I think it would
> > have been cleaner to separate the playground project from Flink core.
> >
> > Cheers,
> > Till
> >
> > On Thu, Aug 8, 2019 at 1:28 PM Konstantin Knauf <
> konstan...@ververica.com>
> > wrote:
> >
> >> Hi Till,
> >>
> >> as Fabian said, we considered the option you mentioned, but in the end
> >> decided that not maintaining a separate images has more advantages.
> >>
> >> In the context of FLIP-42 we are also revisiting the examples in general
> >> and want to clean these up a bit. So, for what it's worth, there will be
> >> an
> >> opportunity for revisiting this topic soon.
> >>
> >> Best,
> >>
> >> Konstantin
> >>
> >>
> >>
> >> On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske 
> wrote:
> >>
> >> > The motivation for including the job as an example is to not have to
> >> > maintain a separate Docker image.
> >> > We would like to use the regular Flink 1.9 image for the playground
> and
> >> > avoid to maintain an image that is slightly different from the regular
> >> 1.9
> >> > image.
> >> >
> >> > Maintaining the job in a different repository or somewhere else would
> >> mean,
> >> > that we need to have a proper release cycle for it as well.
> >> > Having it among the other examples means it's included in the regular
> >> > release.
> >> >
> >> > Best, Fabian
> >> >
> >> >
> >> > Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
> >> > trohrm...@apache.org>:
> >> >
> >> > > Before backporting the playground PR to the release-1.9, I'd like to
> >> > > understand why the ClickEventCount job needs to be part of the Flink
> >> > > distribution. Looking at the example, it seems to only work in
> >> > combination
> >> > > with a Kafka cluster. Since it is not self-contained, it does not
> add
> >> > much
> >> > > value for a user who does not want to use the playgrounds. Moreover,
> >> we
> >> > > already have the StateMachineExample job which can be used to read
> >> from
> >> > > Kafka if a Kafka cluster is available. So my question would be why
> >> don't
> >> > we
> >> > > include the example job in the docker images for the playground?
> This
> >> > would
> >> > > be in my opinion a better separation of concerns.
> >> > >
> >> > > I've cross posted my question on the original PR as well.
> >> > >
> >> > > Cheers,
> >> > > Till
> >> > >
> >> > > On Thu, Aug 8, 2019 at 9:23 AM Kurt Young  wrote:
> >> > >
> >> > > > +1 to include this in 1.9.0, adding some examples doesn't look
> like
> >> new
> >> > > > feature to me.
> >> > > > BTW, I am also trying this tutorial based on release-1.9 branch,
> but
> >> > > > blocked by:
> >> > > >
> >> > > > git clone --branch release-1.10-SNAPSHOT
> >> > > > g...@github.com:apache/flink-playgrounds.git
> >> > > >
> >> > > > Neither 1.10 nor 1.9 exists in flink-playground yet.
> >> > > >
> >> > > > Best,
> >> > > > Kurt
> >> > > >
> >> > > >
> >> > > > On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske 
> >> > wrote:
> >> > > >
> >> > > > > Hi,
> >> > > > > I worked with Konstantin and reviewed the PR.
> >> > > > > I think the playground is a great way to get started with Flink
> >> and
> >> > > > explore
> >> > > > > it's recovery mechanism and unique features like savepoints.
> >> > > > >
> >> > > > > I'm in favor of adding the required streaming example program
> for
> >> the
> >> > > 1.9
> >> > > > > release unless there's a good technical argument against it.
> >> > > > >
> >> > > > > Best, Fabian
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >>
> >> --
> >>
> >> Konstantin Knauf | Solutions Architect
> >>
> >> +49 160 91394525
> >>
> >>
> >> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2019
> >>
> >>
> >> --
> >>
> >> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
> >>
> >> --
> >>
> >> Ververica GmbH
> >> Registered at Amtsgericht Charlotten

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Till Rohrmann]

Just as a short addendum, there are also benefits of having the
ClickEventCount job not being part of the Flink repository. Assume there is
a bug in the job, then you would have to wait for the next Flink release to
fix it.

On Thu, Aug 8, 2019 at 2:24 PM Till Rohrmann  wrote:

> I see that keeping the playground job in the Flink repository has a couple
> of advantages, among other things that it's easier to keep up to date.
> However, in particular in the light of the potential repository split where
> we want to separate connectors from Flink core, it seems very problematic
> to put the ClickEventCount which depends on Flink's Kafka connector in
> Flink's distribution. To me it seems that this was the path of least
> resistance but I'm not sure whether it stays like this. I think it would
> have been cleaner to separate the playground project from Flink core.
>
> Cheers,
> Till
>
> On Thu, Aug 8, 2019 at 1:28 PM Konstantin Knauf 
> wrote:
>
>> Hi Till,
>>
>> as Fabian said, we considered the option you mentioned, but in the end
>> decided that not maintaining a separate images has more advantages.
>>
>> In the context of FLIP-42 we are also revisiting the examples in general
>> and want to clean these up a bit. So, for what it's worth, there will be
>> an
>> opportunity for revisiting this topic soon.
>>
>> Best,
>>
>> Konstantin
>>
>>
>>
>> On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske  wrote:
>>
>> > The motivation for including the job as an example is to not have to
>> > maintain a separate Docker image.
>> > We would like to use the regular Flink 1.9 image for the playground and
>> > avoid to maintain an image that is slightly different from the regular
>> 1.9
>> > image.
>> >
>> > Maintaining the job in a different repository or somewhere else would
>> mean,
>> > that we need to have a proper release cycle for it as well.
>> > Having it among the other examples means it's included in the regular
>> > release.
>> >
>> > Best, Fabian
>> >
>> >
>> > Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
>> > trohrm...@apache.org>:
>> >
>> > > Before backporting the playground PR to the release-1.9, I'd like to
>> > > understand why the ClickEventCount job needs to be part of the Flink
>> > > distribution. Looking at the example, it seems to only work in
>> > combination
>> > > with a Kafka cluster. Since it is not self-contained, it does not add
>> > much
>> > > value for a user who does not want to use the playgrounds. Moreover,
>> we
>> > > already have the StateMachineExample job which can be used to read
>> from
>> > > Kafka if a Kafka cluster is available. So my question would be why
>> don't
>> > we
>> > > include the example job in the docker images for the playground? This
>> > would
>> > > be in my opinion a better separation of concerns.
>> > >
>> > > I've cross posted my question on the original PR as well.
>> > >
>> > > Cheers,
>> > > Till
>> > >
>> > > On Thu, Aug 8, 2019 at 9:23 AM Kurt Young  wrote:
>> > >
>> > > > +1 to include this in 1.9.0, adding some examples doesn't look like
>> new
>> > > > feature to me.
>> > > > BTW, I am also trying this tutorial based on release-1.9 branch, but
>> > > > blocked by:
>> > > >
>> > > > git clone --branch release-1.10-SNAPSHOT
>> > > > g...@github.com:apache/flink-playgrounds.git
>> > > >
>> > > > Neither 1.10 nor 1.9 exists in flink-playground yet.
>> > > >
>> > > > Best,
>> > > > Kurt
>> > > >
>> > > >
>> > > > On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske 
>> > wrote:
>> > > >
>> > > > > Hi,
>> > > > > I worked with Konstantin and reviewed the PR.
>> > > > > I think the playground is a great way to get started with Flink
>> and
>> > > > explore
>> > > > > it's recovery mechanism and unique features like savepoints.
>> > > > >
>> > > > > I'm in favor of adding the required streaming example program for
>> the
>> > > 1.9
>> > > > > release unless there's a good technical argument against it.
>> > > > >
>> > > > > Best, Fabian
>> > > > >
>> > > >
>> > >
>> >
>>
>>
>> --
>>
>> Konstantin Knauf | Solutions Architect
>>
>> +49 160 91394525
>>
>>
>> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2019
>>
>>
>> --
>>
>> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>>
>> --
>>
>> Ververica GmbH
>> Registered at Amtsgericht Charlottenburg: HRB 158244 B
>> Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
>>
>

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Till Rohrmann]

I see that keeping the playground job in the Flink repository has a couple
of advantages, among other things that it's easier to keep up to date.
However, in particular in the light of the potential repository split where
we want to separate connectors from Flink core, it seems very problematic
to put the ClickEventCount which depends on Flink's Kafka connector in
Flink's distribution. To me it seems that this was the path of least
resistance but I'm not sure whether it stays like this. I think it would
have been cleaner to separate the playground project from Flink core.

Cheers,
Till

On Thu, Aug 8, 2019 at 1:28 PM Konstantin Knauf 
wrote:

> Hi Till,
>
> as Fabian said, we considered the option you mentioned, but in the end
> decided that not maintaining a separate images has more advantages.
>
> In the context of FLIP-42 we are also revisiting the examples in general
> and want to clean these up a bit. So, for what it's worth, there will be an
> opportunity for revisiting this topic soon.
>
> Best,
>
> Konstantin
>
>
>
> On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske  wrote:
>
> > The motivation for including the job as an example is to not have to
> > maintain a separate Docker image.
> > We would like to use the regular Flink 1.9 image for the playground and
> > avoid to maintain an image that is slightly different from the regular
> 1.9
> > image.
> >
> > Maintaining the job in a different repository or somewhere else would
> mean,
> > that we need to have a proper release cycle for it as well.
> > Having it among the other examples means it's included in the regular
> > release.
> >
> > Best, Fabian
> >
> >
> > Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
> > trohrm...@apache.org>:
> >
> > > Before backporting the playground PR to the release-1.9, I'd like to
> > > understand why the ClickEventCount job needs to be part of the Flink
> > > distribution. Looking at the example, it seems to only work in
> > combination
> > > with a Kafka cluster. Since it is not self-contained, it does not add
> > much
> > > value for a user who does not want to use the playgrounds. Moreover, we
> > > already have the StateMachineExample job which can be used to read from
> > > Kafka if a Kafka cluster is available. So my question would be why
> don't
> > we
> > > include the example job in the docker images for the playground? This
> > would
> > > be in my opinion a better separation of concerns.
> > >
> > > I've cross posted my question on the original PR as well.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Thu, Aug 8, 2019 at 9:23 AM Kurt Young  wrote:
> > >
> > > > +1 to include this in 1.9.0, adding some examples doesn't look like
> new
> > > > feature to me.
> > > > BTW, I am also trying this tutorial based on release-1.9 branch, but
> > > > blocked by:
> > > >
> > > > git clone --branch release-1.10-SNAPSHOT
> > > > g...@github.com:apache/flink-playgrounds.git
> > > >
> > > > Neither 1.10 nor 1.9 exists in flink-playground yet.
> > > >
> > > > Best,
> > > > Kurt
> > > >
> > > >
> > > > On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske 
> > wrote:
> > > >
> > > > > Hi,
> > > > > I worked with Konstantin and reviewed the PR.
> > > > > I think the playground is a great way to get started with Flink and
> > > > explore
> > > > > it's recovery mechanism and unique features like savepoints.
> > > > >
> > > > > I'm in favor of adding the required streaming example program for
> the
> > > 1.9
> > > > > release unless there's a good technical argument against it.
> > > > >
> > > > > Best, Fabian
> > > > >
> > > >
> > >
> >
>
>
> --
>
> Konstantin Knauf | Solutions Architect
>
> +49 160 91394525
>
>
> Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2019
>
>
> --
>
> Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany
>
> --
>
> Ververica GmbH
> Registered at Amtsgericht Charlottenburg: HRB 158244 B
> Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen
>

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Konstantin Knauf]

Hi Till,

as Fabian said, we considered the option you mentioned, but in the end
decided that not maintaining a separate images has more advantages.

In the context of FLIP-42 we are also revisiting the examples in general
and want to clean these up a bit. So, for what it's worth, there will be an
opportunity for revisiting this topic soon.

Best,

Konstantin



On Thu, Aug 8, 2019 at 11:43 AM Fabian Hueske  wrote:

> The motivation for including the job as an example is to not have to
> maintain a separate Docker image.
> We would like to use the regular Flink 1.9 image for the playground and
> avoid to maintain an image that is slightly different from the regular 1.9
> image.
>
> Maintaining the job in a different repository or somewhere else would mean,
> that we need to have a proper release cycle for it as well.
> Having it among the other examples means it's included in the regular
> release.
>
> Best, Fabian
>
>
> Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
> trohrm...@apache.org>:
>
> > Before backporting the playground PR to the release-1.9, I'd like to
> > understand why the ClickEventCount job needs to be part of the Flink
> > distribution. Looking at the example, it seems to only work in
> combination
> > with a Kafka cluster. Since it is not self-contained, it does not add
> much
> > value for a user who does not want to use the playgrounds. Moreover, we
> > already have the StateMachineExample job which can be used to read from
> > Kafka if a Kafka cluster is available. So my question would be why don't
> we
> > include the example job in the docker images for the playground? This
> would
> > be in my opinion a better separation of concerns.
> >
> > I've cross posted my question on the original PR as well.
> >
> > Cheers,
> > Till
> >
> > On Thu, Aug 8, 2019 at 9:23 AM Kurt Young  wrote:
> >
> > > +1 to include this in 1.9.0, adding some examples doesn't look like new
> > > feature to me.
> > > BTW, I am also trying this tutorial based on release-1.9 branch, but
> > > blocked by:
> > >
> > > git clone --branch release-1.10-SNAPSHOT
> > > g...@github.com:apache/flink-playgrounds.git
> > >
> > > Neither 1.10 nor 1.9 exists in flink-playground yet.
> > >
> > > Best,
> > > Kurt
> > >
> > >
> > > On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske 
> wrote:
> > >
> > > > Hi,
> > > > I worked with Konstantin and reviewed the PR.
> > > > I think the playground is a great way to get started with Flink and
> > > explore
> > > > it's recovery mechanism and unique features like savepoints.
> > > >
> > > > I'm in favor of adding the required streaming example program for the
> > 1.9
> > > > release unless there's a good technical argument against it.
> > > >
> > > > Best, Fabian
> > > >
> > >
> >
>


-- 

Konstantin Knauf | Solutions Architect

+49 160 91394525


Planned Absences: 10.08.2019 - 31.08.2019, 05.09. - 06.09.2019


--

Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany

--

Ververica GmbH
Registered at Amtsgericht Charlottenburg: HRB 158244 B
Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Fabian Hueske]

The motivation for including the job as an example is to not have to
maintain a separate Docker image.
We would like to use the regular Flink 1.9 image for the playground and
avoid to maintain an image that is slightly different from the regular 1.9
image.

Maintaining the job in a different repository or somewhere else would mean,
that we need to have a proper release cycle for it as well.
Having it among the other examples means it's included in the regular
release.

Best, Fabian


Am Do., 8. Aug. 2019 um 09:47 Uhr schrieb Till Rohrmann <
trohrm...@apache.org>:

> Before backporting the playground PR to the release-1.9, I'd like to
> understand why the ClickEventCount job needs to be part of the Flink
> distribution. Looking at the example, it seems to only work in combination
> with a Kafka cluster. Since it is not self-contained, it does not add much
> value for a user who does not want to use the playgrounds. Moreover, we
> already have the StateMachineExample job which can be used to read from
> Kafka if a Kafka cluster is available. So my question would be why don't we
> include the example job in the docker images for the playground? This would
> be in my opinion a better separation of concerns.
>
> I've cross posted my question on the original PR as well.
>
> Cheers,
> Till
>
> On Thu, Aug 8, 2019 at 9:23 AM Kurt Young  wrote:
>
> > +1 to include this in 1.9.0, adding some examples doesn't look like new
> > feature to me.
> > BTW, I am also trying this tutorial based on release-1.9 branch, but
> > blocked by:
> >
> > git clone --branch release-1.10-SNAPSHOT
> > g...@github.com:apache/flink-playgrounds.git
> >
> > Neither 1.10 nor 1.9 exists in flink-playground yet.
> >
> > Best,
> > Kurt
> >
> >
> > On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske  wrote:
> >
> > > Hi,
> > > I worked with Konstantin and reviewed the PR.
> > > I think the playground is a great way to get started with Flink and
> > explore
> > > it's recovery mechanism and unique features like savepoints.
> > >
> > > I'm in favor of adding the required streaming example program for the
> 1.9
> > > release unless there's a good technical argument against it.
> > >
> > > Best, Fabian
> > >
> >
>

Re: [HowTo] Testing Flink Playground (was: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release)

[Kurt Young]

Thanks for the detailed instructions!

Best,
Kurt


On Thu, Aug 8, 2019 at 3:40 PM Fabian Hueske  wrote:

> [Forking off this thread to keep the announce thread "clean"]
>
> Hi Kurt,
>
> The playground needs a bit of manual work at the moment, because 1.9 is
> not released yet.
> The docker-compose and Flink configurations are still in a PR [1].
> Also the Flink 1.9 Docker containers need to manually build. When 1.9 is
> out, we'll publish the container to Docker Hub to make it available as for
> the other Flink versions before.
>
> Instructions to build the container:
>
> 1) backport commit f695a76b10b0cb5f074bbb874fe374cd11e6eff3 to the
> release-1.9 branch
> 2) Build the release-1.9 branch
> 3) clone this repository: https://github.com/docker-flink/docker-flink
> 4) copy the 1.9 build-target folder to docker-flink/1.8/scala_2.11-debian
> 5) change Dockerfile to the content below [2] (between START Dockerfile
> and END Dockerfile)
> 6) Build the Docker container with docker build -t
> flink:1.9-SNAPSHOT-scala_2.11 .
>
> The container is now available and you can follow the steps in the
> playground.
>
> Best, Fabian
>
> [1] https://github.com/apache/flink-playgrounds/pull/1
> [2]
> ### START Dockerfile
>
> ###
> #  Licensed to the Apache Software Foundation (ASF) under one
> #  or more contributor license agreements.  See the NOTICE file
> #  distributed with this work for additional information
> #  regarding copyright ownership.  The ASF licenses this file
> #  to you under the Apache License, Version 2.0 (the
> #  "License"); you may not use this file except in compliance
> #  with the License.  You may obtain a copy of the License at
> #
> #  http://www.apache.org/licenses/LICENSE-2.0
> #
> #  Unless required by applicable law or agreed to in writing, software
> #  distributed under the License is distributed on an "AS IS" BASIS,
> #  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> #  See the License for the specific language governing permissions and
> # limitations under the License.
>
> ###
>
> FROM openjdk:8-jre
>
> # Install dependencies
> RUN set -ex; \
>   apt-get update; \
>   apt-get -y install libsnappy1v5; \
>   rm -rf /var/lib/apt/lists/*
>
> # Grab gosu for easy step-down from root
> ENV GOSU_VERSION 1.11
> RUN set -ex; \
>   wget -nv -O /usr/local/bin/gosu "
> https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$(dpkg
> --print-architecture)"; \
>   wget -nv -O /usr/local/bin/gosu.asc "
> https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$(dpkg
> --print-architecture).asc"; \
>   export GNUPGHOME="$(mktemp -d)"; \
>   for server in ha.pool.sks-keyservers.net $(shuf -e \
>   hkp://p80.pool.sks-keyservers.net:80 \
>   keyserver.ubuntu.com \
>   hkp://keyserver.ubuntu.com:80 \
>   pgp.mit.edu) ; do \
>   gpg --batch --keyserver "$server" --recv-keys
> B42F6819007F00F88E364FD4036A9C25BF357DD4 && break || : ; \
>   done && \
>   gpg --batch --verify /usr/local/bin/gosu.asc /usr/local/bin/gosu; \
>   gpgconf --kill all; \
>   rm -rf "$GNUPGHOME" /usr/local/bin/gosu.asc; \
>   chmod +x /usr/local/bin/gosu; \
>   gosu nobody true
>
> # Configure Flink version
> ENV FLINK_VERSION=1.8.1 \
> HADOOP_SCALA_VARIANT=scala_2.11 \
> GPG_KEY=8FEA1EE9D0048C0CCC70B7573211B0703B79EA0E
>
> # Prepare environment
> ENV FLINK_HOME=/opt/flink
> ENV PATH=$FLINK_HOME/bin:$PATH
> RUN groupadd --system --gid= flink && \
> useradd --system --home-dir $FLINK_HOME --uid= --gid=flink flink
> WORKDIR $FLINK_HOME
>
> ENV
> FLINK_URL_FILE_PATH=flink/flink-${FLINK_VERSION}/flink-${FLINK_VERSION}-bin-${HADOOP_SCALA_VARIANT}.tgz
> # Not all mirrors have the .asc files
> ENV FLINK_TGZ_URL=
> https://www.apache.org/dyn/closer.cgi?action=download&filename=${FLINK_URL_FILE_PATH}
> \
> FLINK_ASC_URL=https://www.apache.org/dist/${FLINK_URL_FILE_PATH}.asc
>
> # Install Flink
> #RUN set -ex; \
> #  wget -nv -O flink.tgz "$FLINK_TGZ_URL"; \
> #  wget -nv -O flink.tgz.asc "$FLINK_ASC_URL"; \
> #  \
> #  export GNUPGHOME="$(mktemp -d)"; \
> #  for server in ha.pool.sks-keyservers.net $(shuf -e \
> #  hkp://p80.pool.sks-keyservers.net:80 \
> #  keyserver.ubuntu.com \
> #  hkp://keyserver.ubuntu.com:80 \
> #  pgp.mit.edu) ; do \
> #  gpg --batch --keyserver "$server" --recv-keys "$GPG_KEY" && break
> || : ; \
> #  done && \
> #  gpg --batch --verify flink.tgz.asc flink.tgz; \
> #  gpgconf --kill all; \
> #  rm -rf "$GNUPGHOME" flink.tgz.asc; \
> #  \
> #  tar -xf flink.tgz --strip-components=1; \
> #  rm flink.tgz; \
> #  \
>
>
> COPY build-target /opt/flink
> RUN  chown -R flink:flink $FLINK_HOME;
>
> # C

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Till Rohrmann]

Before backporting the playground PR to the release-1.9, I'd like to
understand why the ClickEventCount job needs to be part of the Flink
distribution. Looking at the example, it seems to only work in combination
with a Kafka cluster. Since it is not self-contained, it does not add much
value for a user who does not want to use the playgrounds. Moreover, we
already have the StateMachineExample job which can be used to read from
Kafka if a Kafka cluster is available. So my question would be why don't we
include the example job in the docker images for the playground? This would
be in my opinion a better separation of concerns.

I've cross posted my question on the original PR as well.

Cheers,
Till

On Thu, Aug 8, 2019 at 9:23 AM Kurt Young  wrote:

> +1 to include this in 1.9.0, adding some examples doesn't look like new
> feature to me.
> BTW, I am also trying this tutorial based on release-1.9 branch, but
> blocked by:
>
> git clone --branch release-1.10-SNAPSHOT
> g...@github.com:apache/flink-playgrounds.git
>
> Neither 1.10 nor 1.9 exists in flink-playground yet.
>
> Best,
> Kurt
>
>
> On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske  wrote:
>
> > Hi,
> > I worked with Konstantin and reviewed the PR.
> > I think the playground is a great way to get started with Flink and
> explore
> > it's recovery mechanism and unique features like savepoints.
> >
> > I'm in favor of adding the required streaming example program for the 1.9
> > release unless there's a good technical argument against it.
> >
> > Best, Fabian
> >
>

[HowTo] Testing Flink Playground (was: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release)

[Fabian Hueske]

[Forking off this thread to keep the announce thread "clean"]

Hi Kurt,

The playground needs a bit of manual work at the moment, because 1.9 is not
released yet.
The docker-compose and Flink configurations are still in a PR [1].
Also the Flink 1.9 Docker containers need to manually build. When 1.9 is
out, we'll publish the container to Docker Hub to make it available as for
the other Flink versions before.

Instructions to build the container:

1) backport commit f695a76b10b0cb5f074bbb874fe374cd11e6eff3 to the
release-1.9 branch
2) Build the release-1.9 branch
3) clone this repository: https://github.com/docker-flink/docker-flink
4) copy the 1.9 build-target folder to docker-flink/1.8/scala_2.11-debian
5) change Dockerfile to the content below [2] (between START Dockerfile and
END Dockerfile)
6) Build the Docker container with docker build -t
flink:1.9-SNAPSHOT-scala_2.11 .

The container is now available and you can follow the steps in the
playground.

Best, Fabian

[1] https://github.com/apache/flink-playgrounds/pull/1
[2]
### START Dockerfile
###
#  Licensed to the Apache Software Foundation (ASF) under one
#  or more contributor license agreements.  See the NOTICE file
#  distributed with this work for additional information
#  regarding copyright ownership.  The ASF licenses this file
#  to you under the Apache License, Version 2.0 (the
#  "License"); you may not use this file except in compliance
#  with the License.  You may obtain a copy of the License at
#
#  http://www.apache.org/licenses/LICENSE-2.0
#
#  Unless required by applicable law or agreed to in writing, software
#  distributed under the License is distributed on an "AS IS" BASIS,
#  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#  See the License for the specific language governing permissions and
# limitations under the License.
###

FROM openjdk:8-jre

# Install dependencies
RUN set -ex; \
  apt-get update; \
  apt-get -y install libsnappy1v5; \
  rm -rf /var/lib/apt/lists/*

# Grab gosu for easy step-down from root
ENV GOSU_VERSION 1.11
RUN set -ex; \
  wget -nv -O /usr/local/bin/gosu "
https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$(dpkg
--print-architecture)"; \
  wget -nv -O /usr/local/bin/gosu.asc "
https://github.com/tianon/gosu/releases/download/$GOSU_VERSION/gosu-$(dpkg
--print-architecture).asc"; \
  export GNUPGHOME="$(mktemp -d)"; \
  for server in ha.pool.sks-keyservers.net $(shuf -e \
  hkp://p80.pool.sks-keyservers.net:80 \
  keyserver.ubuntu.com \
  hkp://keyserver.ubuntu.com:80 \
  pgp.mit.edu) ; do \
  gpg --batch --keyserver "$server" --recv-keys
B42F6819007F00F88E364FD4036A9C25BF357DD4 && break || : ; \
  done && \
  gpg --batch --verify /usr/local/bin/gosu.asc /usr/local/bin/gosu; \
  gpgconf --kill all; \
  rm -rf "$GNUPGHOME" /usr/local/bin/gosu.asc; \
  chmod +x /usr/local/bin/gosu; \
  gosu nobody true

# Configure Flink version
ENV FLINK_VERSION=1.8.1 \
HADOOP_SCALA_VARIANT=scala_2.11 \
GPG_KEY=8FEA1EE9D0048C0CCC70B7573211B0703B79EA0E

# Prepare environment
ENV FLINK_HOME=/opt/flink
ENV PATH=$FLINK_HOME/bin:$PATH
RUN groupadd --system --gid= flink && \
useradd --system --home-dir $FLINK_HOME --uid= --gid=flink flink
WORKDIR $FLINK_HOME

ENV
FLINK_URL_FILE_PATH=flink/flink-${FLINK_VERSION}/flink-${FLINK_VERSION}-bin-${HADOOP_SCALA_VARIANT}.tgz
# Not all mirrors have the .asc files
ENV FLINK_TGZ_URL=
https://www.apache.org/dyn/closer.cgi?action=download&filename=${FLINK_URL_FILE_PATH}
\
FLINK_ASC_URL=https://www.apache.org/dist/${FLINK_URL_FILE_PATH}.asc

# Install Flink
#RUN set -ex; \
#  wget -nv -O flink.tgz "$FLINK_TGZ_URL"; \
#  wget -nv -O flink.tgz.asc "$FLINK_ASC_URL"; \
#  \
#  export GNUPGHOME="$(mktemp -d)"; \
#  for server in ha.pool.sks-keyservers.net $(shuf -e \
#  hkp://p80.pool.sks-keyservers.net:80 \
#  keyserver.ubuntu.com \
#  hkp://keyserver.ubuntu.com:80 \
#  pgp.mit.edu) ; do \
#  gpg --batch --keyserver "$server" --recv-keys "$GPG_KEY" && break ||
: ; \
#  done && \
#  gpg --batch --verify flink.tgz.asc flink.tgz; \
#  gpgconf --kill all; \
#  rm -rf "$GNUPGHOME" flink.tgz.asc; \
#  \
#  tar -xf flink.tgz --strip-components=1; \
#  rm flink.tgz; \
#  \


COPY build-target /opt/flink
RUN  chown -R flink:flink $FLINK_HOME;

# Configure container
COPY docker-entrypoint.sh /
ENTRYPOINT ["/docker-entrypoint.sh"]
EXPOSE 6123 8081
CMD ["help"]
### END Dockerfile

Am Do., 8. Aug. 2019 um 09:23 Uhr schrieb Kurt Young :

> +1 to include this in 1.9.0, adding some examples doesn't look like new
> feature to me.
> BTW, I am also trying this tutorial based on release-1.9 branch, b

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Kurt Young]

+1 to include this in 1.9.0, adding some examples doesn't look like new
feature to me.
BTW, I am also trying this tutorial based on release-1.9 branch, but
blocked by:

git clone --branch release-1.10-SNAPSHOT
g...@github.com:apache/flink-playgrounds.git

Neither 1.10 nor 1.9 exists in flink-playground yet.

Best,
Kurt


On Thu, Aug 8, 2019 at 3:18 PM Fabian Hueske  wrote:

> Hi,
> I worked with Konstantin and reviewed the PR.
> I think the playground is a great way to get started with Flink and explore
> it's recovery mechanism and unique features like savepoints.
>
> I'm in favor of adding the required streaming example program for the 1.9
> release unless there's a good technical argument against it.
>
> Best, Fabian
>

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Fabian Hueske]

Hi,
I worked with Konstantin and reviewed the PR.
I think the playground is a great way to get started with Flink and explore
it's recovery mechanism and unique features like savepoints.

I'm in favor of adding the required streaming example program for the 1.9
release unless there's a good technical argument against it.

Best, Fabian

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[David Anderson]

I've spent time exploring this playground and its accompanying
documentation, and found it to be a big step forward in making it easy for
folks to experience some of Flink's key features firsthand. From a training
and educational perspective, I'd love to see this in 1.9.

*David Anderson* | Training Coordinator

Follow us @VervericaData
--
Join Flink Forward - The Apache Flink Conference
Stream Processing | Event Driven | Real Time

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Konstantin Knauf]

-Li (Gordon) Tai 于2019年7月30日 周二13:01写道：
> > > >
> > > > > Hi all,
> > > > >
> > > > > There are quite a few instabilities in our builds right now
> (master +
> > > > > release-1.9), some of which are directed or suspiciously related to
> > the
> > > > 1.9
> > > > > release.
> > > > >
> > > > > I'll categorize the instabilities into ones which we were already
> > > > tracking
> > > > > in the 1.9 Burndown Kanban board [1] prior to this email, and which
> > > ones
> > > > > seems to be new or were not monitored so that we draw additional
> > > > attention
> > > > > to them:
> > > > >
> > > > > *Instabilities that were already being tracked*
> > > > >
> > > > > - FLINK-13242: StandaloneResourceManagerTest.testStartupPeriod
> fails
> > on
> > > > > Travis [2]
> > > > > A fix for this is coming with FLINK-13408 (Schedule
> > > > > StandaloneResourceManager.setFailUnfulfillableRequest whenever the
> > > > > leadership is acquired) [3]
> > > > >
> > > > > *New discovered instabilities that we should also start monitoring*
> > > > >
> > > > > - FLINK-13484: ConnectedComponents E2E fails with
> > > > > ResourceNotAvailableException [4]
> > > > > - FLINK-13487:
> > > > >
> > TaskExecutorPartitionLifecycleTest.testPartitionReleaseAfterReleaseCall
> > > > > failed on Travis [5]. FLINK-13476 (Partitions not being properly
> > > released
> > > > > on cancel) could be the cause [6].
> > > > > - FLINK-13488: flink-python fails to build on Travis due to Python
> > 3.3
> > > > > install failure [7]
> > > > > - FLINK-13489: Heavy deployment E2E fails quite consistently on
> > Travis
> > > > with
> > > > > TM heartbeat timeout [8]
> > > > > - FLINK-9900:
> > > > >
> > > >
> > >
> >
> ZooKeeperHighAvailabilityITCase.testRestoreBehaviourWithFaultyStateHandles
> > > > > deadlocks [9]
> > > > > - FLINK-13377: Streaming SQ E2E fails on Travis with mismatching
> > > outputs
> > > > > (could just be that the SQL query tested on Travis is
> > indeterministic)
> > > > [10]
> > > > >
> > > > > Cheers,
> > > > > Gordon
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
> > > > >
> > > > > [2]  https://issues.apache.org/jira/browse/FLINK-13242
> > > > > [3]  https://issues.apache.org/jira/browse/FLINK-13408
> > > > > [4]  https://issues.apache.org/jira/browse/FLINK-13484
> > > > > [5]  https://issues.apache.org/jira/browse/FLINK-13487
> > > > > [6]  https://issues.apache.org/jira/browse/FLINK-13476
> > > > > [7]  https://issues.apache.org/jira/browse/FLINK-13488
> > > > > [8]  https://issues.apache.org/jira/browse/FLINK-13489
> > > > > [9]  https://issues.apache.org/jira/browse/FLINK-9900
> > > > > [10] https://issues.apache.org/jira/browse/FLINK-13377
> > > > >
> > > > > On Sun, Jul 28, 2019 at 6:14 AM zhijiang <
> wangzhijiang...@aliyun.com
> > > > > .invalid>
> > > > > wrote:
> > > > >
> > > > > > Hi Gordon,
> > > > > >
> > > > > > Thanks for the following updates of current progress.
> > > > > > In addition, it might be better to also cover the fix of network
> > > > resource
> > > > > > leak in jira ticket [1] which would be merged soon I think.
> > > > > >
> > > > > > [1] FLINK-13245: This fixes the leak of releasing reader/view
> with
> > > > > > partition in network stack.
> > > > > >
> > > > > > Best,
> > > > > > Zhijiang
> > > > > >
> --
> > > > > > From:Tzu-Li (Gordon) Tai 
> > > > > > Send Time:2019年7月27日(星期六) 10:41
> > > > > > To:dev 
> > > > > > Subject:Re: [ANNOUNCE] Progress updates for Apache 

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

3484: ConnectedComponents E2E fails with
> > > > ResourceNotAvailableException [4]
> > > > - FLINK-13487:
> > > >
> TaskExecutorPartitionLifecycleTest.testPartitionReleaseAfterReleaseCall
> > > > failed on Travis [5]. FLINK-13476 (Partitions not being properly
> > released
> > > > on cancel) could be the cause [6].
> > > > - FLINK-13488: flink-python fails to build on Travis due to Python
> 3.3
> > > > install failure [7]
> > > > - FLINK-13489: Heavy deployment E2E fails quite consistently on
> Travis
> > > with
> > > > TM heartbeat timeout [8]
> > > > - FLINK-9900:
> > > >
> > >
> >
> ZooKeeperHighAvailabilityITCase.testRestoreBehaviourWithFaultyStateHandles
> > > > deadlocks [9]
> > > > - FLINK-13377: Streaming SQ E2E fails on Travis with mismatching
> > outputs
> > > > (could just be that the SQL query tested on Travis is
> indeterministic)
> > > [10]
> > > >
> > > > Cheers,
> > > > Gordon
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
> > > >
> > > > [2]  https://issues.apache.org/jira/browse/FLINK-13242
> > > > [3]  https://issues.apache.org/jira/browse/FLINK-13408
> > > > [4]  https://issues.apache.org/jira/browse/FLINK-13484
> > > > [5]  https://issues.apache.org/jira/browse/FLINK-13487
> > > > [6]  https://issues.apache.org/jira/browse/FLINK-13476
> > > > [7]  https://issues.apache.org/jira/browse/FLINK-13488
> > > > [8]  https://issues.apache.org/jira/browse/FLINK-13489
> > > > [9]  https://issues.apache.org/jira/browse/FLINK-9900
> > > > [10] https://issues.apache.org/jira/browse/FLINK-13377
> > > >
> > > > On Sun, Jul 28, 2019 at 6:14 AM zhijiang  > > > .invalid>
> > > > wrote:
> > > >
> > > > > Hi Gordon,
> > > > >
> > > > > Thanks for the following updates of current progress.
> > > > > In addition, it might be better to also cover the fix of network
> > > resource
> > > > > leak in jira ticket [1] which would be merged soon I think.
> > > > >
> > > > > [1] FLINK-13245: This fixes the leak of releasing reader/view with
> > > > > partition in network stack.
> > > > >
> > > > > Best,
> > > > > Zhijiang
> > > > > --
> > > > > From:Tzu-Li (Gordon) Tai 
> > > > > Send Time:2019年7月27日(星期六) 10:41
> > > > > To:dev 
> > > > > Subject:Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0
> > release
> > > > >
> > > > > Hi all,
> > > > >
> > > > > It's been a while since our last update for the release testing of
> > > 1.9.0,
> > > > > so I want to bring attention to the current status of the release.
> > > > >
> > > > > We are approaching RC1 soon, waiting on the following specific last
> > > > ongoing
> > > > > threads to be closed:
> > > > > - FLINK-13241: This fixes a problem where when using YARN, slot
> > > > allocation
> > > > > requests may be ignored [1]
> > > > > - FLINK-13371: Potential partitions resource leak in case of
> producer
> > > > > restarts [2]
> > > > > - FLINK-13350: Distinguish between temporary tables and persisted
> > > tables
> > > > > [3]. Strictly speaking this would be a new feature, but there was a
> > > > > discussion here [4] to include a workaround for now in 1.9.0, and a
> > > > proper
> > > > > solution later on in 1.10.x.
> > > > > - FLINK-12858: Potential distributed deadlock in case of
> synchronous
> > > > > savepoint failure [5]
> > > > >
> > > > > The above is the critical path for moving forward with an RC1 for
> > > > official
> > > > > voting.
> > > > > All of them have PRs already, and are currently being reviewed or
> > close
> > > > to
> > > > > being merged.
> > > > >
> > > > > Cheers,
> > > > > Gordon
> > > > >
> > > > > [1] https://issues.apache

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Kurt Young]

Update: RC1 for 1.9.0 has been created. Please see [1] for the preview
source / binary releases and Maven artifacts.

Best,
Kurt

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PREVIEW-Apache-Flink-1-9-0-release-candidate-1-td31233.html


On Tue, Jul 30, 2019 at 2:36 PM Tzu-Li (Gordon) Tai 
wrote:

> Hi Biao,
>
> Thanks for working on FLINK-9900. The ticket is already assigned to you
> now.
>
> Cheers,
> Gordon
>
> On Tue, Jul 30, 2019 at 2:31 PM Biao Liu  wrote:
>
> > Hi Gordon,
> >
> > Thanks for updating progress.
> >
> > Currently I'm working on FLINK-9900. I need a committer to assign the
> > ticket to me.
> >
> > Tzu-Li (Gordon) Tai 于2019年7月30日 周二13:01写道：
> >
> > > Hi all,
> > >
> > > There are quite a few instabilities in our builds right now (master +
> > > release-1.9), some of which are directed or suspiciously related to the
> > 1.9
> > > release.
> > >
> > > I'll categorize the instabilities into ones which we were already
> > tracking
> > > in the 1.9 Burndown Kanban board [1] prior to this email, and which
> ones
> > > seems to be new or were not monitored so that we draw additional
> > attention
> > > to them:
> > >
> > > *Instabilities that were already being tracked*
> > >
> > > - FLINK-13242: StandaloneResourceManagerTest.testStartupPeriod fails on
> > > Travis [2]
> > > A fix for this is coming with FLINK-13408 (Schedule
> > > StandaloneResourceManager.setFailUnfulfillableRequest whenever the
> > > leadership is acquired) [3]
> > >
> > > *New discovered instabilities that we should also start monitoring*
> > >
> > > - FLINK-13484: ConnectedComponents E2E fails with
> > > ResourceNotAvailableException [4]
> > > - FLINK-13487:
> > > TaskExecutorPartitionLifecycleTest.testPartitionReleaseAfterReleaseCall
> > > failed on Travis [5]. FLINK-13476 (Partitions not being properly
> released
> > > on cancel) could be the cause [6].
> > > - FLINK-13488: flink-python fails to build on Travis due to Python 3.3
> > > install failure [7]
> > > - FLINK-13489: Heavy deployment E2E fails quite consistently on Travis
> > with
> > > TM heartbeat timeout [8]
> > > - FLINK-9900:
> > >
> >
> ZooKeeperHighAvailabilityITCase.testRestoreBehaviourWithFaultyStateHandles
> > > deadlocks [9]
> > > - FLINK-13377: Streaming SQ E2E fails on Travis with mismatching
> outputs
> > > (could just be that the SQL query tested on Travis is indeterministic)
> > [10]
> > >
> > > Cheers,
> > > Gordon
> > >
> > > [1]
> > >
> > >
> >
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
> > >
> > > [2]  https://issues.apache.org/jira/browse/FLINK-13242
> > > [3]  https://issues.apache.org/jira/browse/FLINK-13408
> > > [4]  https://issues.apache.org/jira/browse/FLINK-13484
> > > [5]  https://issues.apache.org/jira/browse/FLINK-13487
> > > [6]  https://issues.apache.org/jira/browse/FLINK-13476
> > > [7]  https://issues.apache.org/jira/browse/FLINK-13488
> > > [8]  https://issues.apache.org/jira/browse/FLINK-13489
> > > [9]  https://issues.apache.org/jira/browse/FLINK-9900
> > > [10] https://issues.apache.org/jira/browse/FLINK-13377
> > >
> > > On Sun, Jul 28, 2019 at 6:14 AM zhijiang  > > .invalid>
> > > wrote:
> > >
> > > > Hi Gordon,
> > > >
> > > > Thanks for the following updates of current progress.
> > > > In addition, it might be better to also cover the fix of network
> > resource
> > > > leak in jira ticket [1] which would be merged soon I think.
> > > >
> > > > [1] FLINK-13245: This fixes the leak of releasing reader/view with
> > > > partition in network stack.
> > > >
> > > > Best,
> > > > Zhijiang
> > > > --
> > > > From:Tzu-Li (Gordon) Tai 
> > > > Send Time:2019年7月27日(星期六) 10:41
> > > > To:dev 
> > > > Subject:Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0
> release
> > > >
> > > > Hi all,
> > > >
> > > > It's been a while since our last update for the release testing of
> > 1.9.0,
> > > > so I want to bring attention to the current status of the release.

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

Hi Biao,

Thanks for working on FLINK-9900. The ticket is already assigned to you now.

Cheers,
Gordon

On Tue, Jul 30, 2019 at 2:31 PM Biao Liu  wrote:

> Hi Gordon,
>
> Thanks for updating progress.
>
> Currently I'm working on FLINK-9900. I need a committer to assign the
> ticket to me.
>
> Tzu-Li (Gordon) Tai 于2019年7月30日 周二13:01写道：
>
> > Hi all,
> >
> > There are quite a few instabilities in our builds right now (master +
> > release-1.9), some of which are directed or suspiciously related to the
> 1.9
> > release.
> >
> > I'll categorize the instabilities into ones which we were already
> tracking
> > in the 1.9 Burndown Kanban board [1] prior to this email, and which ones
> > seems to be new or were not monitored so that we draw additional
> attention
> > to them:
> >
> > *Instabilities that were already being tracked*
> >
> > - FLINK-13242: StandaloneResourceManagerTest.testStartupPeriod fails on
> > Travis [2]
> > A fix for this is coming with FLINK-13408 (Schedule
> > StandaloneResourceManager.setFailUnfulfillableRequest whenever the
> > leadership is acquired) [3]
> >
> > *New discovered instabilities that we should also start monitoring*
> >
> > - FLINK-13484: ConnectedComponents E2E fails with
> > ResourceNotAvailableException [4]
> > - FLINK-13487:
> > TaskExecutorPartitionLifecycleTest.testPartitionReleaseAfterReleaseCall
> > failed on Travis [5]. FLINK-13476 (Partitions not being properly released
> > on cancel) could be the cause [6].
> > - FLINK-13488: flink-python fails to build on Travis due to Python 3.3
> > install failure [7]
> > - FLINK-13489: Heavy deployment E2E fails quite consistently on Travis
> with
> > TM heartbeat timeout [8]
> > - FLINK-9900:
> >
> ZooKeeperHighAvailabilityITCase.testRestoreBehaviourWithFaultyStateHandles
> > deadlocks [9]
> > - FLINK-13377: Streaming SQ E2E fails on Travis with mismatching outputs
> > (could just be that the SQL query tested on Travis is indeterministic)
> [10]
> >
> > Cheers,
> > Gordon
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
> >
> > [2]  https://issues.apache.org/jira/browse/FLINK-13242
> > [3]  https://issues.apache.org/jira/browse/FLINK-13408
> > [4]  https://issues.apache.org/jira/browse/FLINK-13484
> > [5]  https://issues.apache.org/jira/browse/FLINK-13487
> > [6]  https://issues.apache.org/jira/browse/FLINK-13476
> > [7]  https://issues.apache.org/jira/browse/FLINK-13488
> > [8]  https://issues.apache.org/jira/browse/FLINK-13489
> > [9]  https://issues.apache.org/jira/browse/FLINK-9900
> > [10] https://issues.apache.org/jira/browse/FLINK-13377
> >
> > On Sun, Jul 28, 2019 at 6:14 AM zhijiang  > .invalid>
> > wrote:
> >
> > > Hi Gordon,
> > >
> > > Thanks for the following updates of current progress.
> > > In addition, it might be better to also cover the fix of network
> resource
> > > leak in jira ticket [1] which would be merged soon I think.
> > >
> > > [1] FLINK-13245: This fixes the leak of releasing reader/view with
> > > partition in network stack.
> > >
> > > Best,
> > > Zhijiang
> > > --
> > > From:Tzu-Li (Gordon) Tai 
> > > Send Time:2019年7月27日(星期六) 10:41
> > > To:dev 
> > > Subject:Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release
> > >
> > > Hi all,
> > >
> > > It's been a while since our last update for the release testing of
> 1.9.0,
> > > so I want to bring attention to the current status of the release.
> > >
> > > We are approaching RC1 soon, waiting on the following specific last
> > ongoing
> > > threads to be closed:
> > > - FLINK-13241: This fixes a problem where when using YARN, slot
> > allocation
> > > requests may be ignored [1]
> > > - FLINK-13371: Potential partitions resource leak in case of producer
> > > restarts [2]
> > > - FLINK-13350: Distinguish between temporary tables and persisted
> tables
> > > [3]. Strictly speaking this would be a new feature, but there was a
> > > discussion here [4] to include a workaround for now in 1.9.0, and a
> > proper
> > > solution later on in 1.10.x.
> > > - FLINK-12858: Potential distributed deadlock in case of synchronous
> > > savepoint failure [5]
> > >
> > > The above 

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Biao Liu]

Hi Gordon,

Thanks for updating progress.

Currently I'm working on FLINK-9900. I need a committer to assign the
ticket to me.

Tzu-Li (Gordon) Tai 于2019年7月30日 周二13:01写道：

> Hi all,
>
> There are quite a few instabilities in our builds right now (master +
> release-1.9), some of which are directed or suspiciously related to the 1.9
> release.
>
> I'll categorize the instabilities into ones which we were already tracking
> in the 1.9 Burndown Kanban board [1] prior to this email, and which ones
> seems to be new or were not monitored so that we draw additional attention
> to them:
>
> *Instabilities that were already being tracked*
>
> - FLINK-13242: StandaloneResourceManagerTest.testStartupPeriod fails on
> Travis [2]
> A fix for this is coming with FLINK-13408 (Schedule
> StandaloneResourceManager.setFailUnfulfillableRequest whenever the
> leadership is acquired) [3]
>
> *New discovered instabilities that we should also start monitoring*
>
> - FLINK-13484: ConnectedComponents E2E fails with
> ResourceNotAvailableException [4]
> - FLINK-13487:
> TaskExecutorPartitionLifecycleTest.testPartitionReleaseAfterReleaseCall
> failed on Travis [5]. FLINK-13476 (Partitions not being properly released
> on cancel) could be the cause [6].
> - FLINK-13488: flink-python fails to build on Travis due to Python 3.3
> install failure [7]
> - FLINK-13489: Heavy deployment E2E fails quite consistently on Travis with
> TM heartbeat timeout [8]
> - FLINK-9900:
> ZooKeeperHighAvailabilityITCase.testRestoreBehaviourWithFaultyStateHandles
> deadlocks [9]
> - FLINK-13377: Streaming SQ E2E fails on Travis with mismatching outputs
> (could just be that the SQL query tested on Travis is indeterministic) [10]
>
> Cheers,
> Gordon
>
> [1]
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
>
> [2]  https://issues.apache.org/jira/browse/FLINK-13242
> [3]  https://issues.apache.org/jira/browse/FLINK-13408
> [4]  https://issues.apache.org/jira/browse/FLINK-13484
> [5]  https://issues.apache.org/jira/browse/FLINK-13487
> [6]  https://issues.apache.org/jira/browse/FLINK-13476
> [7]  https://issues.apache.org/jira/browse/FLINK-13488
> [8]  https://issues.apache.org/jira/browse/FLINK-13489
> [9]  https://issues.apache.org/jira/browse/FLINK-9900
> [10] https://issues.apache.org/jira/browse/FLINK-13377
>
> On Sun, Jul 28, 2019 at 6:14 AM zhijiang  .invalid>
> wrote:
>
> > Hi Gordon,
> >
> > Thanks for the following updates of current progress.
> > In addition, it might be better to also cover the fix of network resource
> > leak in jira ticket [1] which would be merged soon I think.
> >
> > [1] FLINK-13245: This fixes the leak of releasing reader/view with
> > partition in network stack.
> >
> > Best,
> > Zhijiang
> > --
> > From:Tzu-Li (Gordon) Tai 
> > Send Time:2019年7月27日(星期六) 10:41
> > To:dev 
> > Subject:Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release
> >
> > Hi all,
> >
> > It's been a while since our last update for the release testing of 1.9.0,
> > so I want to bring attention to the current status of the release.
> >
> > We are approaching RC1 soon, waiting on the following specific last
> ongoing
> > threads to be closed:
> > - FLINK-13241: This fixes a problem where when using YARN, slot
> allocation
> > requests may be ignored [1]
> > - FLINK-13371: Potential partitions resource leak in case of producer
> > restarts [2]
> > - FLINK-13350: Distinguish between temporary tables and persisted tables
> > [3]. Strictly speaking this would be a new feature, but there was a
> > discussion here [4] to include a workaround for now in 1.9.0, and a
> proper
> > solution later on in 1.10.x.
> > - FLINK-12858: Potential distributed deadlock in case of synchronous
> > savepoint failure [5]
> >
> > The above is the critical path for moving forward with an RC1 for
> official
> > voting.
> > All of them have PRs already, and are currently being reviewed or close
> to
> > being merged.
> >
> > Cheers,
> > Gordon
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-13241
> > [2] https://issues.apache.org/jira/browse/FLINK-13371
> > [3] https://issues.apache.org/jira/browse/FLINK-13350
> > [4]
> >
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Support-temporary-tables-in-SQL-API-td30831.html
> > [5] https://issues.apache.org/jira/browse/FLINK-12858
> >
> > On Tue, Jul 16, 2019 at 5:26 AM Tzu

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

Hi all,

There are quite a few instabilities in our builds right now (master +
release-1.9), some of which are directed or suspiciously related to the 1.9
release.

I'll categorize the instabilities into ones which we were already tracking
in the 1.9 Burndown Kanban board [1] prior to this email, and which ones
seems to be new or were not monitored so that we draw additional attention
to them:

*Instabilities that were already being tracked*

- FLINK-13242: StandaloneResourceManagerTest.testStartupPeriod fails on
Travis [2]
A fix for this is coming with FLINK-13408 (Schedule
StandaloneResourceManager.setFailUnfulfillableRequest whenever the
leadership is acquired) [3]

*New discovered instabilities that we should also start monitoring*

- FLINK-13484: ConnectedComponents E2E fails with
ResourceNotAvailableException [4]
- FLINK-13487:
TaskExecutorPartitionLifecycleTest.testPartitionReleaseAfterReleaseCall
failed on Travis [5]. FLINK-13476 (Partitions not being properly released
on cancel) could be the cause [6].
- FLINK-13488: flink-python fails to build on Travis due to Python 3.3
install failure [7]
- FLINK-13489: Heavy deployment E2E fails quite consistently on Travis with
TM heartbeat timeout [8]
- FLINK-9900:
ZooKeeperHighAvailabilityITCase.testRestoreBehaviourWithFaultyStateHandles
deadlocks [9]
- FLINK-13377: Streaming SQ E2E fails on Travis with mismatching outputs
(could just be that the SQL query tested on Travis is indeterministic) [10]

Cheers,
Gordon

[1]
https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328

[2]  https://issues.apache.org/jira/browse/FLINK-13242
[3]  https://issues.apache.org/jira/browse/FLINK-13408
[4]  https://issues.apache.org/jira/browse/FLINK-13484
[5]  https://issues.apache.org/jira/browse/FLINK-13487
[6]  https://issues.apache.org/jira/browse/FLINK-13476
[7]  https://issues.apache.org/jira/browse/FLINK-13488
[8]  https://issues.apache.org/jira/browse/FLINK-13489
[9]  https://issues.apache.org/jira/browse/FLINK-9900
[10] https://issues.apache.org/jira/browse/FLINK-13377

On Sun, Jul 28, 2019 at 6:14 AM zhijiang 
wrote:

> Hi Gordon,
>
> Thanks for the following updates of current progress.
> In addition, it might be better to also cover the fix of network resource
> leak in jira ticket [1] which would be merged soon I think.
>
> [1] FLINK-13245: This fixes the leak of releasing reader/view with
> partition in network stack.
>
> Best,
> Zhijiang
> --
> From:Tzu-Li (Gordon) Tai 
> Send Time:2019年7月27日(星期六) 10:41
> To:dev 
> Subject:Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release
>
> Hi all,
>
> It's been a while since our last update for the release testing of 1.9.0,
> so I want to bring attention to the current status of the release.
>
> We are approaching RC1 soon, waiting on the following specific last ongoing
> threads to be closed:
> - FLINK-13241: This fixes a problem where when using YARN, slot allocation
> requests may be ignored [1]
> - FLINK-13371: Potential partitions resource leak in case of producer
> restarts [2]
> - FLINK-13350: Distinguish between temporary tables and persisted tables
> [3]. Strictly speaking this would be a new feature, but there was a
> discussion here [4] to include a workaround for now in 1.9.0, and a proper
> solution later on in 1.10.x.
> - FLINK-12858: Potential distributed deadlock in case of synchronous
> savepoint failure [5]
>
> The above is the critical path for moving forward with an RC1 for official
> voting.
> All of them have PRs already, and are currently being reviewed or close to
> being merged.
>
> Cheers,
> Gordon
>
> [1] https://issues.apache.org/jira/browse/FLINK-13241
> [2] https://issues.apache.org/jira/browse/FLINK-13371
> [3] https://issues.apache.org/jira/browse/FLINK-13350
> [4]
>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Support-temporary-tables-in-SQL-API-td30831.html
> [5] https://issues.apache.org/jira/browse/FLINK-12858
>
> On Tue, Jul 16, 2019 at 5:26 AM Tzu-Li (Gordon) Tai 
> wrote:
>
> > Update: RC0 for 1.9.0 has been created. Please see [1] for the preview
> > source / binary releases and Maven artifacts.
> >
> > Cheers,
> > Gordon
> >
> > [1]
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PREVIEW-Apache-Flink-1-9-0-release-candidate-0-td30583.html
> >
> > On Mon, Jul 15, 2019 at 6:39 PM Tzu-Li (Gordon) Tai  >
> > wrote:
> >
> >> Hi Flink devs,
> >>
> >> As previously announced by Kurt [1], the release branch for 1.9.0 has
> >> been cut [2] and we've now started the testing phase for this release,
> as
> >> well as resolving remaining block

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[zhijiang]

Hi Gordon,

Thanks for the following updates of current progress. 
In addition, it might be better to also cover the fix of network resource leak 
in jira ticket [1] which would be merged soon I think.

[1] FLINK-13245: This fixes the leak of releasing reader/view with partition in 
network stack.

Best,
Zhijiang
--
From:Tzu-Li (Gordon) Tai 
Send Time:2019年7月27日(星期六) 10:41
To:dev 
Subject:Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

Hi all,

It's been a while since our last update for the release testing of 1.9.0,
so I want to bring attention to the current status of the release.

We are approaching RC1 soon, waiting on the following specific last ongoing
threads to be closed:
- FLINK-13241: This fixes a problem where when using YARN, slot allocation
requests may be ignored [1]
- FLINK-13371: Potential partitions resource leak in case of producer
restarts [2]
- FLINK-13350: Distinguish between temporary tables and persisted tables
[3]. Strictly speaking this would be a new feature, but there was a
discussion here [4] to include a workaround for now in 1.9.0, and a proper
solution later on in 1.10.x.
- FLINK-12858: Potential distributed deadlock in case of synchronous
savepoint failure [5]

The above is the critical path for moving forward with an RC1 for official
voting.
All of them have PRs already, and are currently being reviewed or close to
being merged.

Cheers,
Gordon

[1] https://issues.apache.org/jira/browse/FLINK-13241
[2] https://issues.apache.org/jira/browse/FLINK-13371
[3] https://issues.apache.org/jira/browse/FLINK-13350
[4]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Support-temporary-tables-in-SQL-API-td30831.html
[5] https://issues.apache.org/jira/browse/FLINK-12858

On Tue, Jul 16, 2019 at 5:26 AM Tzu-Li (Gordon) Tai 
wrote:

> Update: RC0 for 1.9.0 has been created. Please see [1] for the preview
> source / binary releases and Maven artifacts.
>
> Cheers,
> Gordon
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PREVIEW-Apache-Flink-1-9-0-release-candidate-0-td30583.html
>
> On Mon, Jul 15, 2019 at 6:39 PM Tzu-Li (Gordon) Tai 
> wrote:
>
>> Hi Flink devs,
>>
>> As previously announced by Kurt [1], the release branch for 1.9.0 has
>> been cut [2] and we've now started the testing phase for this release, as
>> well as resolving remaining blockers.
>>
>> I want to quickly provide an overview of our progress here.
>> Also, over the course of the testing phase, we will update this mail
>> thread every 2-3 days with the overall progress of the release to keep you
>> updated.
>>
>> *1. Remaining blockers and critical issues*
>> You can find a link here [3] for a release Kanban board that provides an
>> overview of the remaining blockers and critical issues for releasing 1.9.0.
>> The issues listed there are high priority for the release, so any help
>> with reviewing or fixing them is highly appreciated!
>> If you do assign yourself to any unassigned issue and start working on
>> it, please make sure to pull it to the "In Progress" column to let others
>> be aware of this.
>>
>> *2. Creating RC 0 for 1.9.0*
>> We will create RC0 now to drive forward the testing efforts.
>> This should be ready by tomorrow morning (July 16, 8am CET).
>> Note that we will not have an official vote for RC0, as this is mainly to
>> drive testing efforts.
>> RC1 with an official vote will be created once the blockers listed in [3]
>> are resolved.
>>
>> Cheers,
>> Gordon
>>
>> [1]
>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Flink-1-9-release-branch-has-been-created-td30500.html
>> [2]
>> https://gitbox.apache.org/repos/asf?p=flink.git;a=shortlog;h=refs/heads/release-1.9
>> [3]
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
>>
>

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

Hi all,

It's been a while since our last update for the release testing of 1.9.0,
so I want to bring attention to the current status of the release.

We are approaching RC1 soon, waiting on the following specific last ongoing
threads to be closed:
- FLINK-13241: This fixes a problem where when using YARN, slot allocation
requests may be ignored [1]
- FLINK-13371: Potential partitions resource leak in case of producer
restarts [2]
- FLINK-13350: Distinguish between temporary tables and persisted tables
[3]. Strictly speaking this would be a new feature, but there was a
discussion here [4] to include a workaround for now in 1.9.0, and a proper
solution later on in 1.10.x.
- FLINK-12858: Potential distributed deadlock in case of synchronous
savepoint failure [5]

The above is the critical path for moving forward with an RC1 for official
voting.
All of them have PRs already, and are currently being reviewed or close to
being merged.

Cheers,
Gordon

[1] https://issues.apache.org/jira/browse/FLINK-13241
[2] https://issues.apache.org/jira/browse/FLINK-13371
[3] https://issues.apache.org/jira/browse/FLINK-13350
[4]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Support-temporary-tables-in-SQL-API-td30831.html
[5] https://issues.apache.org/jira/browse/FLINK-12858

On Tue, Jul 16, 2019 at 5:26 AM Tzu-Li (Gordon) Tai 
wrote:

> Update: RC0 for 1.9.0 has been created. Please see [1] for the preview
> source / binary releases and Maven artifacts.
>
> Cheers,
> Gordon
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PREVIEW-Apache-Flink-1-9-0-release-candidate-0-td30583.html
>
> On Mon, Jul 15, 2019 at 6:39 PM Tzu-Li (Gordon) Tai 
> wrote:
>
>> Hi Flink devs,
>>
>> As previously announced by Kurt [1], the release branch for 1.9.0 has
>> been cut [2] and we've now started the testing phase for this release, as
>> well as resolving remaining blockers.
>>
>> I want to quickly provide an overview of our progress here.
>> Also, over the course of the testing phase, we will update this mail
>> thread every 2-3 days with the overall progress of the release to keep you
>> updated.
>>
>> *1. Remaining blockers and critical issues*
>> You can find a link here [3] for a release Kanban board that provides an
>> overview of the remaining blockers and critical issues for releasing 1.9.0.
>> The issues listed there are high priority for the release, so any help
>> with reviewing or fixing them is highly appreciated!
>> If you do assign yourself to any unassigned issue and start working on
>> it, please make sure to pull it to the "In Progress" column to let others
>> be aware of this.
>>
>> *2. Creating RC 0 for 1.9.0*
>> We will create RC0 now to drive forward the testing efforts.
>> This should be ready by tomorrow morning (July 16, 8am CET).
>> Note that we will not have an official vote for RC0, as this is mainly to
>> drive testing efforts.
>> RC1 with an official vote will be created once the blockers listed in [3]
>> are resolved.
>>
>> Cheers,
>> Gordon
>>
>> [1]
>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Flink-1-9-release-branch-has-been-created-td30500.html
>> [2]
>> https://gitbox.apache.org/repos/asf?p=flink.git;a=shortlog;h=refs/heads/release-1.9
>> [3]
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
>>
>

Re: [ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

Update: RC0 for 1.9.0 has been created. Please see [1] for the preview
source / binary releases and Maven artifacts.

Cheers,
Gordon

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/PREVIEW-Apache-Flink-1-9-0-release-candidate-0-td30583.html

On Mon, Jul 15, 2019 at 6:39 PM Tzu-Li (Gordon) Tai 
wrote:

> Hi Flink devs,
>
> As previously announced by Kurt [1], the release branch for 1.9.0 has been
> cut [2] and we've now started the testing phase for this release, as well
> as resolving remaining blockers.
>
> I want to quickly provide an overview of our progress here.
> Also, over the course of the testing phase, we will update this mail
> thread every 2-3 days with the overall progress of the release to keep you
> updated.
>
> *1. Remaining blockers and critical issues*
> You can find a link here [3] for a release Kanban board that provides an
> overview of the remaining blockers and critical issues for releasing 1.9.0.
> The issues listed there are high priority for the release, so any help
> with reviewing or fixing them is highly appreciated!
> If you do assign yourself to any unassigned issue and start working on it,
> please make sure to pull it to the "In Progress" column to let others be
> aware of this.
>
> *2. Creating RC 0 for 1.9.0*
> We will create RC0 now to drive forward the testing efforts.
> This should be ready by tomorrow morning (July 16, 8am CET).
> Note that we will not have an official vote for RC0, as this is mainly to
> drive testing efforts.
> RC1 with an official vote will be created once the blockers listed in [3]
> are resolved.
>
> Cheers,
> Gordon
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Flink-1-9-release-branch-has-been-created-td30500.html
> [2]
> https://gitbox.apache.org/repos/asf?p=flink.git;a=shortlog;h=refs/heads/release-1.9
> [3]
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
>

[ANNOUNCE] Progress updates for Apache Flink 1.9.0 release

[Tzu-Li (Gordon) Tai]

Hi Flink devs,

As previously announced by Kurt [1], the release branch for 1.9.0 has been
cut [2] and we've now started the testing phase for this release, as well
as resolving remaining blockers.

I want to quickly provide an overview of our progress here.
Also, over the course of the testing phase, we will update this mail thread
every 2-3 days with the overall progress of the release to keep you updated.

*1. Remaining blockers and critical issues*
You can find a link here [3] for a release Kanban board that provides an
overview of the remaining blockers and critical issues for releasing 1.9.0.
The issues listed there are high priority for the release, so any help with
reviewing or fixing them is highly appreciated!
If you do assign yourself to any unassigned issue and start working on it,
please make sure to pull it to the "In Progress" column to let others be
aware of this.

*2. Creating RC 0 for 1.9.0*
We will create RC0 now to drive forward the testing efforts.
This should be ready by tomorrow morning (July 16, 8am CET).
Note that we will not have an official vote for RC0, as this is mainly to
drive testing efforts.
RC1 with an official vote will be created once the blockers listed in [3]
are resolved.

Cheers,
Gordon

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Flink-1-9-release-branch-has-been-created-td30500.html
[2]
https://gitbox.apache.org/repos/asf?p=flink.git;a=shortlog;h=refs/heads/release-1.9
[3]
https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328