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
@@ -120,7 +120,7 @@ az functionapp config appsettings set \
120
120
MEMORY_PROCESSOR_OWNER="durable"
121
121
```
122
122
123
-
`COSMOS_DB_THROUGHPUT_MODE=serverless` is the default and creates the `memories`, `counter`, and `leases` containers without specifying RU/s. Set `COSMOS_DB_THROUGHPUT_MODE=autoscale` to apply the shared `COSMOS_DB_AUTOSCALE_MAX_RU` cap to all required containers.
123
+
`COSMOS_DB_THROUGHPUT_MODE=serverless` is the default and creates the `memories`, `memories_turns`, `memories_summaries`, `counter`, and `leases` containers without specifying RU/s. Set `COSMOS_DB_THROUGHPUT_MODE=autoscale` to apply the shared `COSMOS_DB_AUTOSCALE_MAX_RU` cap to all required containers.
124
124
125
125
`MEMORY_PROCESSOR_OWNER=durable` tells the SDK that the deployed Function App owns processing, so any `CosmosMemoryClient` pointed at the same container will skip its in-process auto-trigger and avoid double-extraction. See the README's processor-ownership table for details.
126
126
@@ -178,7 +178,7 @@ Update `.env` to point at Azure instead of localhost:
This provisions the `memories`, `counter`, and `leases` containers. `serverless` is the default throughput mode; if you set `COSMOS_DB_THROUGHPUT_MODE=autoscale`, the shared `COSMOS_DB_AUTOSCALE_MAX_RU` value is applied to all three containers.
261
+
This provisions the `memories`, `memories_turns`, `memories_summaries`, `counter`, and `leases` containers. `serverless` is the default throughput mode; if you set `COSMOS_DB_THROUGHPUT_MODE=autoscale`, the shared `COSMOS_DB_AUTOSCALE_MAX_RU` value is applied to all five containers.
262
262
263
263
---
264
264
@@ -314,9 +314,9 @@ for i in range(10):
314
314
315
315
# Wait for the change-feed processor to catch up, then read derived memories.
|`leases`|`/id`| Change feed checkpointing container created by `create_memory_store()`|
185
187
186
188
### Throughput configuration
187
189
188
190
The toolkit provisions all required Cosmos containers under one shared throughput mode:
189
191
190
-
-`serverless` is the default. The toolkit creates the `memories`, `counter`, and `leases` containers without specifying RU/s.
191
-
-`autoscale` applies the shared `COSMOS_DB_AUTOSCALE_MAX_RU` cap to all three containers.
192
+
-`serverless` is the default. The toolkit creates the `memories`, `memories_turns`, `memories_summaries`, `counter`, and `leases` containers without specifying RU/s.
193
+
-`autoscale` applies the shared `COSMOS_DB_AUTOSCALE_MAX_RU` cap to all five containers.
192
194
193
195
This keeps the change feed dependencies aligned with the main memory store instead of letting the Functions trigger create the lease container independently.
0 commit comments