Hi everyone, Hi Fabian,
I am also in favor of option 1.
Besides the playgrounds it is a good opportunity to explore this process
for official Docker images as Till suggested. This needs a separate
discussion, though.
Best,
Konstantin
On Fri, Aug 9, 2019 at 5:25 AM Yang Wang wrote:
> Hey
I remember that Patrick (who maintained the docker-flink images so far)
frequently raised the point that its good practice to have the images
decoupled from the project release cycle.
Changes to the images can be done frequently and released fast that way.
In addition, one typically supports
Hey Fabian,
I support option 1.
As per FLIP-42, playgrounds are going to become core to flinks getting started
experience and I believe it is worth the effort to get this right.
- As you mentioned, we may (and in my opinion definitely will) add more images
in the future. Setting up an
One more thing to add.
If we move the code to flink-playgrounds and build custom images, the
playgrounds effort won't be tied to the Flink 1.9 release any more.
So, we'd be a bit more flexible time-wise but would also need to manually
update the playgrounds for every release.
Am Do., 8. Aug. 2019
Hi everyone,
As you might know, some of us are currently working on Docker-based
playgrounds that make it very easy for first-time Flink users to try out
and play with Flink [0].
Our current setup (still work in progress with some parts merged to the
master branch) looks as follows:
* The
