We will not advertise snapshot artifacts to users. This is simply not
allowed by ASF rules.
On 29/04/2020 04:08, Yang Wang wrote:
Thanks for starting this discussion.
In general, i am also in favor of making docker image release could be
partly decoupled from Flink release. However, i think it
Thanks for starting this discussion.
In general, i am also in favor of making docker image release could be
partly decoupled from Flink release. However, i think it should only happen
when we want to make some changes that are independent from Flink
majar release(e.g. JDK11, change base image, ins
> To me this means that the docker images should be released at the same time
> the other artifacts are released. This also includes shapshot releases. So
> the build of the docker images should be an integral part of the build.
This is already the case since the last release, what this thread i
I agree with Niels that if a Flink release is made it should be
accompanied by the Dockerfiles for that version, and release them at once.
This makes sense for testing purposes alone, and I view Docker as just
another distribution channel like Maven central.
The reverse isn't necessarily true tho
Hi Niels,
I think Robert was referring to the fact that Apache considers only the
source release to be "the release", everything else is called
convenience release.
Best,
Aljoscha
On 27.04.20 19:43, Niels Basjes wrote:
Hi,
In my opinion the docker images are essentially simply differently
Hi,
In my opinion the docker images are essentially simply differently packed
binary releases.
This becomes more true when in the future deploying a Flink application to
kubernetes simply pulls the correct binary from a docker hub. Because of
these kinds of use cases I disagree with Robert that t
Thanks for starting the thread!
I would consider the docker images of Flink convenience binary releases
that can happen any time. I believe a simplified, but formal release
process would be appropriate (preview / staging images for the community to
validate & vote, then release to docker hub).
On
We can create additional releases independent of Flink, but they will
have to go through a formal release process in any case.
On 22/04/2020 14:55, Ismaël Mejía wrote:
Hello,
I wanted to discuss about a subject that was shortly mentioned during the docker
unification thread (and in some other
maybe could try someway like foreachpartition in foreachrdd,which will not
together to driver take too extra consumption. xiaoxingstack
邮箱：xiaoxingst...@gmail.com 签名由 网易邮箱大师 定制 On 04/22/2020 20:55, Ismaël Mejía
wrote: Hello, I wanted to discuss about a subject that was shortly mentioned
during
I am confused why docker upstream can influence inner process seriously,may be
the jvm thread?In my opinion,docker is just a child space of os. xiaoxingstack
邮箱：xiaoxingst...@gmail.com 签名由 网易邮箱大师 定制 On 04/22/2020 20:55, Ismaël Mejía
wrote: Hello, I wanted to discuss about a subject that was shor
Hello,
I wanted to discuss about a subject that was shortly mentioned during the docker
unification thread (and in some other PR) that is the release of docker images
independent of major Flink releases.
In the past when the docker images were maintained outside of the Apache
repository we usuall
11 matches
Mail list logo
