Hi all, The FLIP was updated under the section "First Version Deliverables".
Cheers, Kostas On Tue, Mar 10, 2020 at 4:10 PM Kostas Kloudas <kklou...@gmail.com> wrote: > > Hi all, > > Yes I will do that. From the discussion, I will add that: > 1) for the cli, we are planning to add a "run-application" command > 2) for deployment in Yarn we are planning to use LocalResources to let > Yarn do the jar transfer > 3) for Standalone/containers, we assume that dependencies/jars are > built into the image. > > Cheers, > Kostas > > On Tue, Mar 10, 2020 at 3:05 PM Yang Wang <danrtsey...@gmail.com> wrote: > > > > Thanks for your response. > > > > @Kostas Kloudas Could we update the cli changes and how to fetch the > > user jars to FLIP document? I think other dev or users may have the similar > > questions. > > > > > > Best, > > Yang > > > > Aljoscha Krettek <aljos...@apache.org> 于2020年3月10日周二 下午9:03写道： > >> > >> On 10.03.20 03:31, Yang Wang wrote: > >> > For the "run-job", do you mean to submit a Flink job to an existing > >> > session > >> > or > >> > just like the current per-job to start a dedicated Flink cluster? Then > >> > will > >> > "flink run" be deprecated? > >> > >> I was talking about the per-job mode that starts a dedicated Flink > >> cluster. This was more thinking about the future but it might make sense > >> to separate these modes more. "flink run" would then only be used for > >> submitting to a session cluster, on standalone or K8s or whatnot. > >> > >> > On Yarn deployment, we could register the local or HDFS jar/files > >> > as LocalResource. > >> > And let Yarn to localize the resource to workdir, when the entrypoint is > >> > launched, all > >> > the jars and dependencies exist locally. So the entrypoint will *NOT* do > >> > the real fetching, > >> > do i understand correctly? > >> > >> Yes, this is exactly what I meant. > >> > >> Best, > >> Aljoscha
