public static final class SubscriberGrpc.SubscriberStub extends AbstractAsyncStub<SubscriberGrpc.SubscriberStub>
A stub to allow clients to do asynchronous rpc calls to service Subscriber.
The service that an application uses to manipulate subscriptions and to
consume messages from a subscription via the Pull method or by
establishing a bi-directional stream using the StreamingPull method.
Inheritance
java.lang.Object >
io.grpc.stub.AbstractStub >
io.grpc.stub.AbstractAsyncStub >
SubscriberGrpc.SubscriberStub
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
acknowledge(AcknowledgeRequest request, StreamObserver<Empty> responseObserver)
public void acknowledge(AcknowledgeRequest request, StreamObserver<Empty> responseObserver)
Acknowledges the messages associated with the ack_ids in the
AcknowledgeRequest. The Pub/Sub system can remove the relevant messages
from the subscription.
Acknowledging a message whose ack deadline has expired may succeed,
but such a message may be redelivered later. Acknowledging a message more
than once will not result in an error.
build(Channel channel, CallOptions callOptions)
protected SubscriberGrpc.SubscriberStub 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)
createSnapshot(CreateSnapshotRequest request, StreamObserver<Snapshot> responseObserver)
public void createSnapshot(CreateSnapshotRequest request, StreamObserver<Snapshot> responseObserver)
Creates a snapshot from the requested subscription. Snapshots are used in
Seek operations,
which allow you to manage message acknowledgments in bulk. That is, you can
set the acknowledgment state of messages in an existing subscription to the
state captured by a snapshot.
If the snapshot already exists, returns ALREADY_EXISTS.
If the requested subscription doesn't exist, returns NOT_FOUND.
If the backlog in the subscription is too old -- and the resulting snapshot
would expire in less than 1 hour -- then FAILED_PRECONDITION is returned.
See also the Snapshot.expire_time field. If the name is not provided in
the request, the server will assign a random
name for this snapshot on the same project as the subscription, conforming
to the resource name format. The
generated name is populated in the returned Snapshot object. Note that for
REST API requests, you must specify a name in the request.
createSubscription(Subscription request, StreamObserver<Subscription> responseObserver)
public void createSubscription(Subscription request, StreamObserver<Subscription> responseObserver)
Creates a subscription to a given topic. See the resource name rules.
If the subscription already exists, returns ALREADY_EXISTS.
If the corresponding topic doesn't exist, returns NOT_FOUND.
If the name is not provided in the request, the server will assign a random
name for this subscription on the same project as the topic, conforming
to the resource name format. The
generated name is populated in the returned Subscription object. Note that
for REST API requests, you must specify a name in the request.
deleteSnapshot(DeleteSnapshotRequest request, StreamObserver<Empty> responseObserver)
public void deleteSnapshot(DeleteSnapshotRequest request, StreamObserver<Empty> responseObserver)
Removes an existing snapshot. Snapshots are used in Seek operations, which
allow you to manage message acknowledgments in bulk. That is, you can set
the acknowledgment state of messages in an existing subscription to the
state captured by a snapshot.
When the snapshot is deleted, all messages retained in the snapshot
are immediately dropped. After a snapshot is deleted, a new one may be
created with the same name, but the new one has no association with the old
snapshot or its subscription, unless the same subscription is specified.
deleteSubscription(DeleteSubscriptionRequest request, StreamObserver<Empty> responseObserver)
public void deleteSubscription(DeleteSubscriptionRequest request, StreamObserver<Empty> responseObserver)
Deletes an existing subscription. All messages retained in the subscription
are immediately dropped. Calls to Pull after deletion will return
NOT_FOUND. After a subscription is deleted, a new one may be created with
the same name, but the new one has no association with the old
subscription or its topic unless the same topic is specified.
getSnapshot(GetSnapshotRequest request, StreamObserver<Snapshot> responseObserver)
public void getSnapshot(GetSnapshotRequest request, StreamObserver<Snapshot> responseObserver)
Gets the configuration details of a snapshot. Snapshots are used in
Seek operations,
which allow you to manage message acknowledgments in bulk. That is, you can
set the acknowledgment state of messages in an existing subscription to the
state captured by a snapshot.
getSubscription(GetSubscriptionRequest request, StreamObserver<Subscription> responseObserver)
public void getSubscription(GetSubscriptionRequest request, StreamObserver<Subscription> responseObserver)
Gets the configuration details of a subscription.
listSnapshots(ListSnapshotsRequest request, StreamObserver<ListSnapshotsResponse> responseObserver)
public void listSnapshots(ListSnapshotsRequest request, StreamObserver<ListSnapshotsResponse> responseObserver)
Lists the existing snapshots. Snapshots are used in Seek operations, which
allow you to manage message acknowledgments in bulk. That is, you can set
the acknowledgment state of messages in an existing subscription to the
state captured by a snapshot.
listSubscriptions(ListSubscriptionsRequest request, StreamObserver<ListSubscriptionsResponse> responseObserver)
public void listSubscriptions(ListSubscriptionsRequest request, StreamObserver<ListSubscriptionsResponse> responseObserver)
Lists matching subscriptions.
modifyAckDeadline(ModifyAckDeadlineRequest request, StreamObserver<Empty> responseObserver)
public void modifyAckDeadline(ModifyAckDeadlineRequest request, StreamObserver<Empty> responseObserver)
Modifies the ack deadline for a specific message. This method is useful
to indicate that more time is needed to process a message by the
subscriber, or to make the message available for redelivery if the
processing was interrupted. Note that this does not modify the
subscription-level ackDeadlineSeconds used for subsequent messages.
modifyPushConfig(ModifyPushConfigRequest request, StreamObserver<Empty> responseObserver)
public void modifyPushConfig(ModifyPushConfigRequest request, StreamObserver<Empty> responseObserver)
Modifies the PushConfig for a specified subscription.
This may be used to change a push subscription to a pull one (signified by
an empty PushConfig) or vice versa, or change the endpoint URL and other
attributes of a push subscription. Messages will accumulate for delivery
continuously through the call regardless of changes to the PushConfig.
pull(PullRequest request, StreamObserver<PullResponse> responseObserver)
public void pull(PullRequest request, StreamObserver<PullResponse> responseObserver)
Pulls messages from the server.
seek(SeekRequest request, StreamObserver<SeekResponse> responseObserver)
public void seek(SeekRequest request, StreamObserver<SeekResponse> responseObserver)
Seeks an existing subscription to a point in time or to a given snapshot,
whichever is provided in the request. Snapshots are used in Seek operations, which
allow you to manage message acknowledgments in bulk. That is, you can set
the acknowledgment state of messages in an existing subscription to the
state captured by a snapshot. Note that both the subscription and the
snapshot must be on the same topic.
streamingPull(StreamObserver<StreamingPullResponse> responseObserver)
public StreamObserver<StreamingPullRequest> streamingPull(StreamObserver<StreamingPullResponse> responseObserver)
Establishes a stream with the server, which sends messages down to the
client. The client streams acknowledgements and ack deadline modifications
back to the server. The server will close the stream and return the status
on any error. The server may close the stream with status UNAVAILABLE to
reassign server-side resources, in which case, the client should
re-establish the stream. Flow control can be achieved by configuring the
underlying RPC channel.
updateSnapshot(UpdateSnapshotRequest request, StreamObserver<Snapshot> responseObserver)
public void updateSnapshot(UpdateSnapshotRequest request, StreamObserver<Snapshot> responseObserver)
Updates an existing snapshot by updating the fields specified in the update
mask. Snapshots are used in
Seek operations,
which allow you to manage message acknowledgments in bulk. That is, you can
set the acknowledgment state of messages in an existing subscription to the
state captured by a snapshot.
updateSubscription(UpdateSubscriptionRequest request, StreamObserver<Subscription> responseObserver)
public void updateSubscription(UpdateSubscriptionRequest request, StreamObserver<Subscription> responseObserver)
Updates an existing subscription by updating the fields specified in the
update mask. Note that certain properties of a subscription, such as its
topic, are not modifiable.
