StreamingPullRequest

JSON representation

Request for the StreamingPull streaming RPC method. This request is used to establish the initial stream as well as to stream acknowledgements and ack deadline modifications from the client to the server.

JSON representation
{ "subscription": string, "ackIds": [ string ], "modifyDeadlineSeconds": [ integer ], "modifyDeadlineAckIds": [ string ], "streamAckDeadlineSeconds": integer, "clientId": string, "maxOutstandingMessages": string, "maxOutstandingBytes": string }

JSON representation

{
  "subscription": string,
  "ackIds": [
    string
  ],
  "modifyDeadlineSeconds": [
    integer
  ],
  "modifyDeadlineAckIds": [
    string
  ],
  "streamAckDeadlineSeconds": integer,
  "clientId": string,
  "maxOutstandingMessages": string,
  "maxOutstandingBytes": string
}

Fields
`subscription`	`string` Required. The subscription for which to initialize the new stream. This must be provided in the first request on the stream, and must not be set in subsequent requests from client to server. Format is `projects/{project}/subscriptions/{sub}`.
`ackIds[]`	`string` Optional. List of acknowledgement IDs for acknowledging previously received messages (received on this stream or a different stream). If an ack ID has expired, the corresponding message may be redelivered later. Acknowledging a message more than once will not result in an error. If the acknowledgement ID is malformed, the stream will be aborted with status `INVALID_ARGUMENT`.
`modifyDeadlineSeconds[]`	`integer` Optional. The list of new ack deadlines for the IDs listed in `modifyDeadlineAckIds`. The size of this list must be the same as the size of `modifyDeadlineAckIds`. If it differs the stream will be aborted with `INVALID_ARGUMENT`. Each element in this list is applied to the element in the same position in `modifyDeadlineAckIds`. The new ack deadline is with respect to the time this request was sent to the Pub/Sub system. Must be >= 0. For example, if the value is 10, the new ack deadline will expire 10 seconds after this request is received. If the value is 0, the message is immediately made available for another streaming or non-streaming pull request. If the value is < 0 (an error), the stream will be aborted with status `INVALID_ARGUMENT`.
`modifyDeadlineAckIds[]`	`string` Optional. List of acknowledgement IDs whose deadline will be modified based on the corresponding element in `modifyDeadlineSeconds`. This field can be used 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.
`streamAckDeadlineSeconds`	`integer` Required. The ack deadline to use for the stream. This must be provided in the first request on the stream, but it can also be updated on subsequent requests from client to server. The minimum deadline you can specify is 10 seconds. The maximum deadline you can specify is 600 seconds (10 minutes).
`clientId`	`string` Optional. A unique identifier that is used to distinguish client instances from each other. Only needs to be provided on the initial request. When a stream disconnects and reconnects for the same stream, the clientId should be set to the same value so that state associated with the old stream can be transferred to the new stream. The same clientId should not be used for different client instances.
`maxOutstandingMessages`	`string (int64 format)` Optional. Flow control settings for the maximum number of outstanding messages. When there are `maxOutstandingMessages` currently sent to the streaming pull client that have not yet been acked or nacked, the server stops sending more messages. The sending of messages resumes once the number of outstanding messages is less than this value. If the value is <= 0, there is no limit to the number of outstanding messages. This property can only be set on the initial StreamingPullRequest. If it is set on a subsequent request, the stream will be aborted with status `INVALID_ARGUMENT`.
`maxOutstandingBytes`	`string (int64 format)` Optional. Flow control settings for the maximum number of outstanding bytes. When there are `maxOutstandingBytes` or more worth of messages currently sent to the streaming pull client that have not yet been acked or nacked, the server will stop sending more messages. The sending of messages resumes once the number of outstanding bytes is less than this value. If the value is <= 0, there is no limit to the number of outstanding bytes. This property can only be set on the initial StreamingPullRequest. If it is set on a subsequent request, the stream will be aborted with status `INVALID_ARGUMENT`.