A stub to allow clients to do synchronous rpc calls to service WorkflowTemplateService.
The API interface for managing Workflow Templates in the
Dataproc API.
Inherited Members
io.grpc.stub.AbstractBlockingStub.<T>newStub(io.grpc.stub.AbstractStub.StubFactory<T>,io.grpc.Channel)
io.grpc.stub.AbstractBlockingStub.<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(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()
Instantiates a template and begins execution.
This method is equivalent to executing the sequence
CreateWorkflowTemplate,
InstantiateWorkflowTemplate,
DeleteWorkflowTemplate.
The returned Operation can be used to track execution of
workflow by polling
operations.get.
The Operation will complete when entire workflow is finished.
The running workflow can be aborted via
operations.cancel.
This will cause any inflight jobs to be cancelled and workflow-owned
clusters to be deleted.
The Operation.metadata will be
WorkflowMetadata.
Also see Using
WorkflowMetadata.
On successful completion,
Operation.response will be
Empty.
Instantiates a template and begins execution.
The returned Operation can be used to track execution of
workflow by polling
operations.get.
The Operation will complete when entire workflow is finished.
The running workflow can be aborted via
operations.cancel.
This will cause any inflight jobs to be cancelled and workflow-owned
clusters to be deleted.
The Operation.metadata will be
WorkflowMetadata.
Also see Using
WorkflowMetadata.
On successful completion,
Operation.response will be
Empty.