A stub to allow clients to do synchronous rpc calls to service BigQueryWrite.
BigQuery Write API.
The Write API can be used to write data to BigQuery.
For supplementary information about the Write API, see:
https://cloud.google.com/bigquery/docs/write-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()
Atomically commits a group of PENDING streams that belong to the same
parent table.
Streams must be finalized before commit and cannot be committed multiple
times. Once a stream is committed, data in the stream becomes available
for read operations.
Creates a write stream to the given table.
Additionally, every table has a special stream named '_default'
to which data can be written. This stream doesn't need to be created using
CreateWriteStream. It is a stream that can be used simultaneously by any
number of clients. Data written to this stream is considered committed as
soon as an acknowledgement is received.
Flushes rows to a BUFFERED stream.
If users are appending rows to BUFFERED stream, flush operation is
required in order for the rows to become available for reading. A
Flush operation flushes up to any previously flushed offset in a BUFFERED
stream, to the offset specified in the request.
Flush is not supported on the _default stream, since it is not BUFFERED.
