#Rest on us how to
This example shows how to change the manual throughput (RU/s) of a collection to 1000 RU/s. It is a system-generated property that specifies the resource etag required for optimistic concurrency control. It is the unique addressable URI for the resource. It specifies the last updated timestamp of the resource. For V2 offers, it contains the throughput of the collection. Its set to Invalid for user-defined performance levels. Pre-defined performance levels S1, S2, or S3 for V1 Offers. This value can be V1 for pre-defined throughput levels and V2 for user-defined throughput levels. Refer to the "x-ms-retry-after-ms response" header to see how long you should wait before retrying this operation. The replace offer is throttled because the offer scale down operation is attempted within the idle timeout period, that is 4 hours. The offer is no longer a resource, that is, the resource was deleted. 401 is also returned when the Authorization header is set to an invalid authorization token. The Authorization or x-ms-date header is not set. Check for missing curly brackets or quotes.
#Rest on us full
For a full list of status codes, see HTTP Status Codes. The following table lists common status codes returned by this operation. See Common Azure Cosmos DB REST response headers for headers that are returned by all Cosmos DB responses. "resource": "dbs/rgkVAA=/colls/rgkVAMHcJww=/", It is used internally for placement and navigation of the offer. The resource ID ( _rid) is a unique identifier that is also hierarchical per the resource stack on the resource model.
It has the same value as the _rid for the offer. The ID for the offer resource is automatically generated when it is created.
In the example above, the _rid for the collection is pLJdAOlEdgA=. When creating a new collection, this property is set to the self-link of the collection for example, dbs/pLJdAA=/colls/pLJdAOlEdgA=/.ĭuring creation of a collection, this property is automatically associated to the resource ID, that is, _rid of the collection. It is invalid for user-defined performance levels or provisioned throughput based model.Ĭontains information about the offer – for V2 offers, this value contains the throughput of the collection. Set it to S1, S2, or S3 for V1 offer types. This property is only applicable in the V1 offer version. It can be V1 for the legacy S1, S2, and S3 levels and V2 for user-defined throughput levels (recommended). See Common Azure Cosmos DB REST request headers for headers that are used by all Cosmos DB requests Body Property Typically, a database _rid is length 8, a collection _rid is length 12, and an offer _rid is length 4. Then, query the offers to find the _rid-offer that corresponds to the database or collection's _rid. To find the _rid of the offer associated with a database or collection, first GET the database or GET the collection and note the _rid property of the resource.
0 kommentar(er)
