public static final class BigQueryWriteGrpc.BigQueryWriteStub extends AbstractAsyncStub<BigQueryWriteGrpc.BigQueryWriteStub>
A stub to allow clients to do asynchronous 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
Inheritance
java.lang.Object >
io.grpc.stub.AbstractStub >
io.grpc.stub.AbstractAsyncStub >
BigQueryWriteGrpc.BigQueryWriteStub
Inherited Members
io.grpc.stub.AbstractAsyncStub.<T>newStub(io.grpc.stub.AbstractStub.StubFactory<T>,io.grpc.Channel)
io.grpc.stub.AbstractAsyncStub.<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()
Methods
appendRows(StreamObserver<AppendRowsResponse> responseObserver)
public StreamObserver<AppendRowsRequest> appendRows(StreamObserver<AppendRowsResponse> responseObserver)
Appends data to the given stream.
If offset is specified, the offset is checked against the end of
stream. The server returns OUT_OF_RANGE in AppendRowsResponse if an
attempt is made to append to an offset beyond the current end of the stream
or ALREADY_EXISTS if user provides an offset that has already been
written to. User can retry with adjusted offset within the same RPC
connection. If offset is not specified, append happens at the end of the
stream.
The response contains an optional offset at which the append
happened. No offset information will be returned for appends to a
default stream.
Responses are received in the same order in which requests are sent.
There will be one response for each successful inserted request. Responses
may optionally embed error information if the originating AppendRequest was
not successfully processed.
The specifics of when successfully appended data is made visible to the
table are governed by the type of stream:
- For COMMITTED streams (which includes the default stream), data is
visible immediately upon successful append.
- For BUFFERED streams, data is made visible via a subsequent
FlushRows
rpc which advances a cursor to a newer offset in the stream.
- For PENDING streams, data is not made visible until the stream itself is
finalized (via the
FinalizeWriteStream rpc), and the stream is explicitly
committed via the BatchCommitWriteStreams rpc.
| Parameter |
| Name |
Description |
responseObserver |
io.grpc.stub.StreamObserver<AppendRowsResponse>
|
batchCommitWriteStreams(BatchCommitWriteStreamsRequest request, StreamObserver<BatchCommitWriteStreamsResponse> responseObserver)
public void batchCommitWriteStreams(BatchCommitWriteStreamsRequest request, StreamObserver<BatchCommitWriteStreamsResponse> responseObserver)
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.
build(Channel channel, CallOptions callOptions)
protected BigQueryWriteGrpc.BigQueryWriteStub build(Channel channel, CallOptions callOptions)
| Parameters |
| Name |
Description |
channel |
io.grpc.Channel
|
callOptions |
io.grpc.CallOptions
|
Overrides
io.grpc.stub.AbstractStub.build(io.grpc.Channel,io.grpc.CallOptions)
createWriteStream(CreateWriteStreamRequest request, StreamObserver<WriteStream> responseObserver)
public void createWriteStream(CreateWriteStreamRequest request, StreamObserver<WriteStream> responseObserver)
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.
finalizeWriteStream(FinalizeWriteStreamRequest request, StreamObserver<FinalizeWriteStreamResponse> responseObserver)
public void finalizeWriteStream(FinalizeWriteStreamRequest request, StreamObserver<FinalizeWriteStreamResponse> responseObserver)
Finalize a write stream so that no new data can be appended to the
stream. Finalize is not supported on the '_default' stream.
flushRows(FlushRowsRequest request, StreamObserver<FlushRowsResponse> responseObserver)
public void flushRows(FlushRowsRequest request, StreamObserver<FlushRowsResponse> responseObserver)
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.
getWriteStream(GetWriteStreamRequest request, StreamObserver<WriteStream> responseObserver)
public void getWriteStream(GetWriteStreamRequest request, StreamObserver<WriteStream> responseObserver)
Gets information about a write stream.
