Azure Cosmos DB

Dapr doesn’t transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see . You can directly interact with the underlying store to manipulate the state data, such as:

• Creating aggregated views.
• Making backups.

Note

Azure Cosmos DB is a multi-modal database that supports multiple APIs. The default Dapr Cosmos DB state store implementation uses the .

To connect to your Cosmos DB instance, you can either:

• Use the Data Explorer on .

Note

To get all state keys associated with application “myapp”, use the query:

The above query returns all documents with an id containing “myapp-”, which is the prefix of the state keys.

To get the state data by a key “balance” for the application “myapp”, use the query:

To get all the state keys associated with an actor with the instance ID “leroy” of actor type “cat” belonging to the application with ID “mypets”, use the command:

And to get a specific actor state such as “food”, use the command:

Warning

You should not manually update or delete states in the store. All writes and delete operations should be done via the Dapr runtime. The only exception: it is often required to delete actor records in a state store, once you know that these are no longer in use, to prevent a build up of unused actor instances that may never be loaded again.