/// 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.
///
/// Note: For users coding against the gRPC api directly, it may be
/// necessary to supply the x-goog-request-params system parameter
/// with `write_stream=<full_write_stream_name>`.
///
/// More information about system parameters:
/// https://cloud.google.com/apis/docs/system-parameters
Appends data to the given stream.
If `offset` is specified, the `offset` is checked against the end of
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.

For users coding against the gRPC api directly, it may be
necessary to supply the x-goog-request-params system parameter
with `write_stream=`.


Appends data to the given stream . If ` offset ` is specified the ` offset ` is checked against the end of 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 . For users coding against the gRPC api directly it may be necessary to supply the x - goog - request - params system parameter with ` write_stream = ` .
pub async fn append_rows(
            &mut self,
            request: impl tonic::IntoStreamingRequest<Message = super::AppendRowsRequest>,
        ) -> Result<
            tonic::Response<tonic::codec::Streaming<super::AppendRowsResponse>>,
            tonic::Status,
        > {
            self.inner
                .ready()
                .await
                .map_err(|e| {
                    tonic::Status::new(
                        tonic::Code::Unknown,
                        format!("Service was not ready: {}", e.into()),
                    )
                })?;
            let codec = tonic::codec::ProstCodec::default();
            let path = http::uri::PathAndQuery::from_static(
                "/google.cloud.bigquery.storage.v1.BigQueryWrite/AppendRows",
            );
            self.inner.streaming(request.into_streaming_request(), path, codec).await
        }
pub async fn append_rows ( & mut self , request : impl tonic :: IntoStreamingRequest < Message = super :: AppendRowsRequest > , ) -> Result < tonic :: Response < tonic :: codec :: Streaming < super :: AppendRowsResponse > > , tonic :: Status , > { self . inner . ready ( ) . await . map_err ( | e | { tonic :: Status :: new ( tonic :: Code :: Unknown , format ! ( " " e into ( ) ) , ) } ) ? ; let codec = tonic :: codec :: ProstCodec :: default ( ) ; let path = http :: uri :: PathAndQuery :: from_static ( " " , ) ; self . inner . streaming ( request . into_streaming_request ( ) , path , codec ) . await }
Appends data to the given stream.
Appends data to the given stream .
&mut self
request
impl tonic::IntoStreamingRequest<Message = super::AppendRowsRequest>