Hi everyone, We have an Azure Cosmos DB container that gets populated with batched entries and currently they get sorted by the "c_ts" JSON value. I would like them to be sorted by "creationDate" value in Oldest to Newest order. Is there a way I can do that, maybe with the Indexing Policy for that container? Kind regards Chris.

Chris Buley Thank you for clarifying this. Yes, the indexing policy you’ve provided aims to sort the entries in your Azure Cosmos DB container by the “creationDate” value in Oldest to Newest order. { "automatic":true, "indexingMode":"Consistent", "includedPaths":[ { "path":"/*" } ], "excludedPaths":[], "compositeIndexes":[ [ { "path":"/creationDate", "order":"ascending" } ] } Manage indexing policies in Azure Cosmos DB Regards, Oury

Azure Cosmos DB container sorting of records

Accepted answer

Oury Ba-MSFT 16,391 Reputation points Microsoft Employee

2024-02-21T18:26:33.3233333+00:00

Chris Buley Thank you for clarifying this. Yes, the indexing policy you’ve provided aims to sort the entries in your Azure Cosmos DB container by the “creationDate” value in Oldest to Newest order. { "automatic":true, "indexingMode":"Consistent", "includedPaths":[ { "path":"/*" } ], "excludedPaths":[], "compositeIndexes":[ [ { "path":"/creationDate", "order":"ascending" } ] } Manage indexing policies in Azure Cosmos DB Regards, Oury
Please sign in to rate this answer.
Oury Ba-MSFT 16,391 Reputation points Microsoft Employee

2024-02-21T18:27:29.99+00:00

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Chris Buley 26 Reputation points

2024-02-21T19:06:21.0766667+00:00

Awesome, many thanks for your clarification Oury.

Oury Ba-MSFT 16,391 Reputation points Microsoft Employee

2024-02-21T20:08:14.3166667+00:00

It was a pleasure helping you Chris Buley Regards, Oury

Priya Ponnuram 0 Reputation points

2024-04-02T15:50:24.5733333+00:00

{ "automatic":true, "indexingMode":"Consistent", "includedPaths":[ { "path":"/*" } ], "excludedPaths":[], "compositeIndexes":[ [ { "path":"/creationDate", "order":"ascending" } ] }

The above won't work as composite indexes require 2 paths!

Oury Ba-MSFT 16,391 Reputation points Microsoft Employee

2024-04-29T20:06:39.7866667+00:00

Priya Ponnuram

The provided indexing policy indeed has a single composite index on the “creationDate” field in ascending order. However, you are correct that composite indexes typically require at least two paths.

Here’s an updated indexing policy that includes both the “creationDate” field and another field (e.g., “id” or “partitionKey”):

JSON

{ "automatic": true, "indexingMode": "Consistent", "includedPaths": [ { "path": "/creationDate/?", "indexes": [ { "kind": "Range", "dataType": "Number", "precision": -1, "min": "-9223372036854775808", "max": "9223372036854775807" }, { "kind": "Hash", "dataType": "String", "precision": 3 } ] }, { "path": "/id/?" } ], "excludedPaths": [] }

You can adjust the second path according to your specific requirements.Regards,

Oury
Sign in to comment

Azure Cosmos DB container sorting of records

0 additional answers