s consensus, so it's probably ready to
>>> share
>>> :)
>>>
>>> >> On Fri, May 18, 2018 at 3:00 PM Ankur Goenka
>>> wrote:
>>>
>>> >>> Thanks for all the input.
>>> >>> I have summarized the discussion
gt;>> >> 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
>>> wrote:
>>>
>>> >>> Thanks for all the input.
>>>
e 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 impor
8 at 12:34 PM Ankur Goenka
> wrote:
>
> >>>>> Updated link to the document as the previous link was not working for
> some people.
>
>
> >>>>> On Fri, May 11, 2018 at 7:56 PM Ankur Goenka
> 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
>
as the previous link was not working for
some people.
>>>>> On Fri, May 11, 2018 at 7:56 PM Ankur Goenka
wrote:
>>>>>> Hi,
>>>>>> Recent effort on portability has introduced JobService and
ArtifactService to the beam stack along with SDK. This
ous link was not working for some people.
>>>>
>>>>
>>>> On Fri, May 11, 2018 at 7:56 PM Ankur Goenka wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Recent effort on portability has introduced JobService and
>>>&
ri, May 11, 2018 at 7:56 PM Ankur Goenka 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 arou
> 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
>>>
>>
ort 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
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 disc
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
11 matches
Mail list logo
