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 Fabi
Hey Fabian,
Sounds great! It will be more easier to build an end-to-end play ground
with docker.
I prefer option 1.
We need to build the official docker images and push to docker hub after
every version is released. It could be used to play with docker compose,
kubernetes, etc.
Today we coul
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 image
I would be in favour of option 1.
We could also think about making the flink-playgrounds and the Flink docker
image release part of the Flink release process [1] if we don't want to
have independent release cycles. I think at the moment the official Flink
docker image is too often forgotten.
[1]
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 integr
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
