A stub to allow clients to do ListenableFuture-style rpc calls to service TemplatesService.
Provides a method to create Cloud Dataflow jobs from templates.
Inherited Members
io.grpc.stub.AbstractFutureStub.<T>newStub(io.grpc.stub.AbstractStub.StubFactory<T>,io.grpc.Channel)
io.grpc.stub.AbstractFutureStub.<T>newStub(io.grpc.stub.AbstractStub.StubFactory<T>,io.grpc.Channel,io.grpc.CallOptions)
io.grpc.stub.AbstractStub.<T>withOption(io.grpc.CallOptions.Key<T>,T)
io.grpc.stub.AbstractStub.build(io.grpc.Channel,io.grpc.CallOptions)
io.grpc.stub.AbstractStub.getCallOptions()
io.grpc.stub.AbstractStub.getChannel()
io.grpc.stub.AbstractStub.withCallCredentials(io.grpc.CallCredentials)
io.grpc.stub.AbstractStub.withChannel(io.grpc.Channel)
io.grpc.stub.AbstractStub.withCompression(java.lang.String)
io.grpc.stub.AbstractStub.withDeadline(io.grpc.Deadline)
io.grpc.stub.AbstractStub.withDeadlineAfter(java.time.Duration)
io.grpc.stub.AbstractStub.withDeadlineAfter(long,java.util.concurrent.TimeUnit)
io.grpc.stub.AbstractStub.withExecutor(java.util.concurrent.Executor)
io.grpc.stub.AbstractStub.withInterceptors(io.grpc.ClientInterceptor...)
io.grpc.stub.AbstractStub.withMaxInboundMessageSize(int)
io.grpc.stub.AbstractStub.withMaxOutboundMessageSize(int)
io.grpc.stub.AbstractStub.withOnReadyThreshold(int)
io.grpc.stub.AbstractStub.withWaitForReady()
Creates a Cloud Dataflow job from a template. Do not enter confidential
information when you supply string values using the API.
To create a job, we recommend using projects.locations.templates.create
with a regional endpoint. Using
projects.templates.create is not recommended, because your job will
always start in us-central1.
Get the template associated with a template.
To get the template, we recommend using projects.locations.templates.get
with a regional endpoint. Using
projects.templates.get is not recommended, because only
templates that are running in us-central1 are retrieved.
Launches a template.
To launch a template, we recommend using
projects.locations.templates.launch with a regional endpoint. Using
projects.templates.launch is not recommended, because jobs launched
from the template will always start in us-central1.