View Source API Reference google_api_pub_sub_lite v0.9.0

Modules

API client metadata for GoogleApi.PubSubLite.V1.

API calls for all endpoints tagged Admin.

API calls for all endpoints tagged Cursor.

API calls for all endpoints tagged TopicStats.

Handle Tesla connections for GoogleApi.PubSubLite.V1.

The request message for Operations.CancelOperation.

The throughput capacity configuration for each partition.

Compute the current head cursor for a partition.

Response containing the head cursor for the requested topic and partition.

Compute statistics about a range of messages in a given topic and partition.

Response containing stats for messages in the requested topic and partition.

Compute the corresponding cursor for a publish or event time in a topic partition.

Response containing the cursor corresponding to a publish or event time in a topic partition.

A cursor that describes the position of a message within a topic partition.

The settings for a subscription's message delivery.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Configuration for a Pub/Sub Lite subscription that writes messages to a destination. User subscriber clients must not connect to this subscription.

The response message for Operations.ListOperations.

This resource represents a long-running operation that is the result of a network API call.

Metadata for long running operations.

The settings for a topic's partitions.

A pair of a Cursor and the partition it is for.

Configuration for exporting to a Pub/Sub topic.

Metadata about a reservation resource.

The settings for this topic's Reservation usage.

The settings for a topic's message retention.

Response for SeekSubscription long running operation.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

Metadata about a subscription resource.

A target publish or event time. Can be used for seeking to or retrieving the corresponding cursor.

Metadata about a topic resource.

Response for GetTopicPartitions.