Thanks Ankur, I think there's consensus, so it's probably ready to share :)
On Fri, May 18, 2018 at 3:00 PM Ankur Goenka <goe...@google.com> wrote: > Thanks for all the input. > I have summarized the discussions at the bottom of the document ( here > <https://docs.google.com/document/d/1xOaEEJrMmiSHprd-WiYABegfT129qqF-idUBINjxz8s/edit#heading=h.lky5ef6wxo9x> > ). > Please feel free to provide comments. > Once we agree, I will publish the conclusion on the mailing list. > > On Mon, May 14, 2018 at 1:51 PM Eugene Kirpichov <kirpic...@google.com> > wrote: > >> Thanks Ankur, this document clarifies a few points and raises some very >> important questions. I encourage everybody with a stake in Portability to >> take a look and chime in. >> >> +Aljoscha Krettek <aljos...@data-artisans.com> +Thomas Weise >> <t...@apache.org> +Henning Rohde <hero...@google.com> >> >> On Mon, May 14, 2018 at 12:34 PM Ankur Goenka <goe...@google.com> wrote: >> >>> Updated link >>> <https://docs.google.com/document/d/1xOaEEJrMmiSHprd-WiYABegfT129qqF-idUBINjxz8s/edit> >>> to >>> the document as the previous link was not working for some people. >>> >>> >>> On Fri, May 11, 2018 at 7:56 PM Ankur Goenka <goe...@google.com> wrote: >>> >>>> Hi, >>>> >>>> Recent effort on portability has introduced JobService and >>>> ArtifactService to the beam stack along with SDK. This has open up a few >>>> questions around how we start a pipeline in a portable setup (with >>>> JobService). >>>> I am trying to document our approach to launching a portable pipeline >>>> and take binding decisions based on the discussion. >>>> Please review the document and provide your feedback. >>>> >>>> Thanks, >>>> Ankur >>>> >>>
