You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/pubsublite_v1.admin.projects.locations.topics.html
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ <h3>Method Details</h3>
125
125
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
126
126
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
127
127
},
128
-
"count": "A String", # The number of partitions in the topic. Must be at least 1.
128
+
"count": "A String", # The number of partitions in the topic. Must be at least 1. Once a topic has been created the number of partitions can be increased but not decreased. Message ordering is not guaranteed across a topic resize. For more information see https://cloud.google.com/pubsub/lite/docs/topics#scaling_capacity
129
129
"scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
130
130
},
131
131
"retentionConfig": { # The settings for a topic's message retention. # The settings for this topic's message retention.
@@ -150,7 +150,7 @@ <h3>Method Details</h3>
150
150
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
151
151
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
152
152
},
153
-
"count": "A String", # The number of partitions in the topic. Must be at least 1.
153
+
"count": "A String", # The number of partitions in the topic. Must be at least 1. Once a topic has been created the number of partitions can be increased but not decreased. Message ordering is not guaranteed across a topic resize. For more information see https://cloud.google.com/pubsub/lite/docs/topics#scaling_capacity
154
154
"scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
155
155
},
156
156
"retentionConfig": { # The settings for a topic's message retention. # The settings for this topic's message retention.
@@ -199,7 +199,7 @@ <h3>Method Details</h3>
199
199
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
200
200
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
201
201
},
202
-
"count": "A String", # The number of partitions in the topic. Must be at least 1.
202
+
"count": "A String", # The number of partitions in the topic. Must be at least 1. Once a topic has been created the number of partitions can be increased but not decreased. Message ordering is not guaranteed across a topic resize. For more information see https://cloud.google.com/pubsub/lite/docs/topics#scaling_capacity
203
203
"scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
204
204
},
205
205
"retentionConfig": { # The settings for a topic's message retention. # The settings for this topic's message retention.
@@ -254,7 +254,7 @@ <h3>Method Details</h3>
254
254
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
255
255
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
256
256
},
257
-
"count": "A String", # The number of partitions in the topic. Must be at least 1.
257
+
"count": "A String", # The number of partitions in the topic. Must be at least 1. Once a topic has been created the number of partitions can be increased but not decreased. Message ordering is not guaranteed across a topic resize. For more information see https://cloud.google.com/pubsub/lite/docs/topics#scaling_capacity
258
258
"scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
259
259
},
260
260
"retentionConfig": { # The settings for a topic's message retention. # The settings for this topic's message retention.
@@ -296,7 +296,7 @@ <h3>Method Details</h3>
296
296
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
297
297
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
298
298
},
299
-
"count": "A String", # The number of partitions in the topic. Must be at least 1.
299
+
"count": "A String", # The number of partitions in the topic. Must be at least 1. Once a topic has been created the number of partitions can be increased but not decreased. Message ordering is not guaranteed across a topic resize. For more information see https://cloud.google.com/pubsub/lite/docs/topics#scaling_capacity
300
300
"scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
301
301
},
302
302
"retentionConfig": { # The settings for a topic's message retention. # The settings for this topic's message retention.
@@ -321,7 +321,7 @@ <h3>Method Details</h3>
321
321
"publishMibPerSec": 42, # Publish throughput capacity per partition in MiB/s. Must be >= 4 and <= 16.
322
322
"subscribeMibPerSec": 42, # Subscribe throughput capacity per partition in MiB/s. Must be >= 4 and <= 32.
323
323
},
324
-
"count": "A String", # The number of partitions in the topic. Must be at least 1.
324
+
"count": "A String", # The number of partitions in the topic. Must be at least 1. Once a topic has been created the number of partitions can be increased but not decreased. Message ordering is not guaranteed across a topic resize. For more information see https://cloud.google.com/pubsub/lite/docs/topics#scaling_capacity
325
325
"scale": 42, # DEPRECATED: Use capacity instead which can express a superset of configurations. Every partition in the topic is allocated throughput equivalent to `scale` times the standard partition throughput (4 MiB/s). This is also reflected in the cost of this topic; a topic with `scale` of 2 and count of 10 is charged for 20 partitions. This value must be in the range [1,4].
326
326
},
327
327
"retentionConfig": { # The settings for a topic's message retention. # The settings for this topic's message retention.
<pclass="firstline">Compute the head cursor for the partition. The head cursor’s offset is guaranteed to be before or equal to all messages which have not yet been acknowledged to be published, and greater than the offset of any message whose publish has already been acknowledged. It is 0 if there have never been messages on the partition.</p>
<pre>Compute the head cursor for the partition. The head cursor’s offset is guaranteed to be before or equal to all messages which have not yet been acknowledged to be published, and greater than the offset of any message whose publish has already been acknowledged. It is 0 if there have never been messages on the partition.
95
+
96
+
Args:
97
+
topic: string, Required. The topic for which we should compute the head cursor. (required)
98
+
body: object, The request body.
99
+
The object takes the form of:
100
+
101
+
{ # Compute the current head cursor for a partition.
102
+
"partition": "A String", # Required. The partition for which we should compute the head cursor.
103
+
}
104
+
105
+
x__xgafv: string, V1 error format.
106
+
Allowed values
107
+
1 - v1 error format
108
+
2 - v2 error format
109
+
110
+
Returns:
111
+
An object of the form:
112
+
113
+
{ # Response containing the head cursor for the requested topic and partition.
114
+
"headCursor": { # A cursor that describes the position of a message within a topic partition. # The head cursor.
115
+
"offset": "A String", # The offset of a message within a topic partition. Must be greater than or equal 0.
0 commit comments