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://a
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
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
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 conv
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
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
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
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 reposi
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
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
[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
+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-playgr
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 technic
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* | Trainin
t; > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=FLINK&rapidView=328
> > > > >
> > > > > [2] 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.apa
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:
> > >
> > > > H
LINK-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 o
> 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,
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 f
.
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 testi
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 usi
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-L
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 pha
24 matches
Mail list logo