The message data field. If this field is empty, the message must contain at least one attribute.
Attributes for this message. If this field is empty, the message must contain non-empty data. This can be used to filter messages on the subscription.
ID of this message, assigned by the server when the message is published.
Guaranteed to be unique within the topic. This value may be read by a
subscriber that receives a PubsubMessage
via a Pull
call or a push
delivery. It must not be populated by the publisher in a Publish
call.
The time at which the message was published, populated by the server when
it receives the Publish
call. It must not be populated by the
publisher in a Publish
call.
If non-empty, identifies related messages for which publish order should be
respected. If a Subscription
has enable_message_ordering
set to true
,
messages published with the same non-empty ordering_key
value will be
delivered to subscribers in the order in which they are received by the
Pub/Sub system. All PubsubMessage
s published in a given PublishRequest
must specify the same ordering_key
value.
Attributes for this message.
Attributes for this message. If this field is empty, the message must contain non-empty data. This can be used to filter messages on the subscription.
The message data field.
The message data field. If this field is empty, the message must contain at least one attribute.
ID of this message, assigned by the server when the message is published.
ID of this message, assigned by the server when the message is published.
Guaranteed to be unique within the topic. This value may be read by a
subscriber that receives a PubsubMessage
via a Pull
call or a push
delivery. It must not be populated by the publisher in a Publish
call.
If non-empty, identifies related messages for which publish order should be respected.
If non-empty, identifies related messages for which publish order should be
respected. If a Subscription
has enable_message_ordering
set to true
,
messages published with the same non-empty ordering_key
value will be
delivered to subscribers in the order in which they are received by the
Pub/Sub system. All PubsubMessage
s published in a given PublishRequest
must specify the same ordering_key
value.
The time at which the message was published, populated by the server when
it receives the Publish
call.
The time at which the message was published, populated by the server when
it receives the Publish
call. It must not be populated by the
publisher in a Publish
call.
(Since version 0.6.0) Use toPMessage
(Since version 0.6.0) Use getField that accepts a ScalaPB descriptor and returns PValue
A message that is published by publishers and consumed by subscribers. The message must contain either a non-empty data field or at least one attribute. Note that client libraries represent this object differently depending on the language. See the corresponding [client library documentation](https://cloud.google.com/pubsub/docs/reference/libraries) for more information. See [quotas and limits] (https://cloud.google.com/pubsub/quotas) for more information about message limits.
The message data field. If this field is empty, the message must contain at least one attribute.
Attributes for this message. If this field is empty, the message must contain non-empty data. This can be used to filter messages on the subscription.
ID of this message, assigned by the server when the message is published. Guaranteed to be unique within the topic. This value may be read by a subscriber that receives a
PubsubMessage
via aPull
call or a push delivery. It must not be populated by the publisher in aPublish
call.The time at which the message was published, populated by the server when it receives the
Publish
call. It must not be populated by the publisher in aPublish
call.If non-empty, identifies related messages for which publish order should be respected. If a
Subscription
hasenable_message_ordering
set totrue
, messages published with the same non-emptyordering_key
value will be delivered to subscribers in the order in which they are received by the Pub/Sub system. AllPubsubMessage
s published in a givenPublishRequest
must specify the sameordering_key
value.