Thanks for the link, Steve - very helpful!
On Mon, Oct 12, 2020 at 11:31 AM Steve Niemitz wrote:
> This is what I was referencing:
> https://github.com/googleapis/google-api-java-client-services/tree/master/clients/google-api-services-dataflow/v1b3
>
>
>
>
> On Mon, Oct 12, 2020 at 2:23 PM
This is what I was referencing:
https://github.com/googleapis/google-api-java-client-services/tree/master/clients/google-api-services-dataflow/v1b3
On Mon, Oct 12, 2020 at 2:23 PM Peter Littig
wrote:
> Thanks for the replies, Lukasz and Steve!
>
> Steve: do you have a link to the google
Thanks for the replies, Lukasz and Steve!
Steve: do you have a link to the google client api wrappers (I'm not sure
if I know what they are.)
Thank you!
On Mon, Oct 12, 2020 at 11:04 AM Steve Niemitz wrote:
> We use the Dataflow API [1] directly, via the google api client wrappers
> (both
We use the Dataflow API [1] directly, via the google api client wrappers
(both python and java), pretty extensively. It works well and doesn't
require a dependency on beam.
[1] https://cloud.google.com/dataflow/docs/reference/rest
On Mon, Oct 12, 2020 at 1:56 PM Luke Cwik wrote:
> It is your
It is your best way to do this right now and this hasn't changed in a while
(region was added to project and job ids in the past 6 years).
On Mon, Oct 12, 2020 at 10:53 AM Peter Littig
wrote:
> Thanks for the reply, Kyle.
>
> The DataflowClient::getJob method uses a Dataflow instance that's
Thanks for the reply, Kyle.
The DataflowClient::getJob method uses a Dataflow instance that's provided
at construction time (via DataflowPipelineOptions::getDataflowClient). If
that Dataflow instance can be obtained from a minimal instance of the
options (i.e., containing only the project ID and
> I think the answer is to use a DataflowClient in the second service, but
creating one requires DataflowPipelineOptions. Are these options supposed
to be exactly the same as those used by the first service? Or do only some
of the fields have to be the same?
Most options are not necessary for
