Hi Chesnay,
thanks for joining the discussion. For clarification: the repository will
only contain a docker-compose.yaml and a few configuration files. In terms
of Flink images the plan is to use `library/flink:`
[1].
Best,
Konstantin
[1] https://github.com/docker-flink/docker-flink
On Fri,
The last time this came up was about our download page which contained
snapshot links, with a big warning that these are for dev purposes, and
we had to take that down. Back than the conclusion was that snapshot
artifacts must only be linked on pages intended for developers, and most
not be
That's a good point. We should point readers in the documentation to the
repository first, and then write "for convenience, you can also download a
snapshot of the repository here" AND put a disclaimer on the page, that
this archive is not an official product released by the Flink PMC.
Since this
Wouldn't this qualify for releasing snapshot artifacts to users? (Which,
you know, shouldn't be done?)
On 12/07/2019 11:55, Robert Metzger wrote:
I will request the repo now, so that you can continue working on the
documentation (thanks for that again :) )
I actually like Xuefu's idea of
Thanks Robert. I will prepare the first PR early next week.
On Fri, Jul 12, 2019 at 11:58 AM Robert Metzger wrote:
> The repo creation was faster than expected:
> https://github.com/apache/flink-playgrounds (it's not even listed here
> yet:
> https://gitbox.apache.org/repos/asf)
>
>
> On Fri,
The repo creation was faster than expected:
https://github.com/apache/flink-playgrounds (it's not even listed here yet:
https://gitbox.apache.org/repos/asf)
On Fri, Jul 12, 2019 at 11:55 AM Robert Metzger wrote:
> I will request the repo now, so that you can continue working on the
>
I will request the repo now, so that you can continue working on the
documentation (thanks for that again :) )
I actually like Xuefu's idea of making an archive available.
The good thing is that we can get this from any GitHub hosted repository.
For example for Flink, this link let's you
Hi everyone,
thanks everyone for you remarks and questions! We have three +1s, so I
think, we can proceed with this.
@Robert: Could you create the request to the INFRA?
Thanks,
Konstantin
On Fri, Jul 12, 2019 at 10:16 AM Stephan Ewen wrote:
> I am fine with a separate repository, was just
I am fine with a separate repository, was just raising the other option as
a question.
+1 to go ahead
On Fri, Jul 12, 2019 at 9:49 AM Konstantin Knauf
wrote:
> Hi Xuefu,
>
> thanks for having a look at this. I am sure this playground setup will need
> to be maintained and will go through
Hi Xuefu,
thanks for having a look at this. I am sure this playground setup will need
to be maintained and will go through revisions, too. So, we would still
need to keep the content of the archive in some repository + the additional
piece of automation to update the archive, when the
The idea seems interesting, but I'm wondering if we have considered
publishing .tz file hosted somewhere in Flink site with a link in the doc.
This might avoid the "overkill" of introducing a repo, which is main used
for version control in development cycles. On the other hand, a docker
setup,
Hi Stephan,
putting it under "flink-quickstarts" alone would not help. The user would
still need to check out the whole `apache/flink` repository, which is a bit
overwhelming. The Java/Scala quickstarts use Maven archetypes. Is this what
you are suggesting? I think, this would be an option, but
Hi all!
I am fine with a separate repository.
Quick question. though: Have you considered putting the setup not under
"docs" but under "flink-quickstart" or so?
Would that be equally cumbersome for users?
Best,
Stephan
On Thu, Jul 11, 2019 at 12:19 PM Fabian Hueske wrote:
> Hi,
>
> I think
Hi,
I think Quickstart should be as lightweight as possible and follow common
practices.
A Git repository for a few configuration files might feel like overkill,
but IMO it makes sense because this ensures users can get started with 3
commands:
$ git clone .../flink-playground
$ cd
+1 to create a repo.
On Thu, Jul 11, 2019 at 11:10 AM Konstantin Knauf
wrote:
> Hi everyone,
>
> in the course of implementing FLIP-42 we are currently reworking the
> Getting Started section of our documentation. As part of this, we are
> adding docker-compose-based playgrounds to get started
Hi everyone,
in the course of implementing FLIP-42 we are currently reworking the
Getting Started section of our documentation. As part of this, we are
adding docker-compose-based playgrounds to get started with Flink
operations and Flink SQL quickly.
To reduce as much friction as possible for
16 matches
Mail list logo
