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
[Cosmos] Add max_integrated_cache_staleness param option to item methods (Azure#22946)
* consistency level gets set to default found in database account
* async client default change
* updated docs based on finding and updated samples to reflect best practices
* Update CHANGELOG.md
* Update README.md
* Update README.md
* Update README.md
* Update CHANGELOG.md
* formatting
* formatting
* updated consistency for first request to Eventual (lowest latency)
* pylint
* from_connection_string methods
* from_connection_string2
* Update sdk/cosmos/azure-cosmos/README.md
Co-authored-by: Gahl Levy <[email protected]>
* Apply suggestions from code review
Co-authored-by: Gahl Levy <[email protected]>
* Update README.md
* removed forceful header usage, changed setup to only check for Session consistency to start client session
* need to set header if Session consistency for updating session if needed (thanks Jake!)
* Apply suggestions from code review
Kushagra improved documentation and comments
Co-authored-by: Kushagra Thapar <[email protected]>
* added test for session token
* Update CHANGELOG.md
* Update _cosmos_client_connection_async.py
* added max_integrated_cache_staleness to item methods in containers
* added validation and provisional comments
* pylint
* only applied to read-only operations
* Update container.py
* Update CHANGELOG.md
* Apply suggestions from code review
Co-authored-by: Kushagra Thapar <[email protected]>
* Update _base.py
* updated param comments to mention integrated cache configuration
* moved to kwargs
* added tests to verify functionality
* Update test_integrated_cache.py
* Update test_integrated_cache.py
* updates to test to ensure it works with setup
* added headers test and new way to track client headers before sending out
these changes will also likely be used for creating the diagnostics later on
* Update test_integrated_cache.py
* Create test_axq.py
* Added mocking tests for max integrated cache staleness. Fixed issue with int value being false
* upgrade version for release
Co-authored-by: Gahl Levy <[email protected]>
Co-authored-by: Kushagra Thapar <[email protected]>
Co-authored-by: Kushagra Thapar <[email protected]>
Copy file name to clipboardExpand all lines: sdk/cosmos/azure-cosmos/CHANGELOG.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,17 @@
12
12
> for more details on consistency levels, or the README section on this change [here](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos#note-on-client-consistency-levels).
13
13
14
14
#### Features Added
15
-
- Added support for split-proof queries for the async client.
15
+
- Added new **provisional**`max_integrated_cache_staleness_in_ms` parameter to read item and query items APIs in order
16
+
to make use of the **preview** CosmosDB integrated cache functionality.
17
+
Please see [Azure Cosmos DB integrated cache](https://docs.microsoft.com/azure/cosmos-db/integrated-cache) for more details.
18
+
- Added support for split-proof queries for the async client
16
19
17
20
### Bugs fixed
18
-
- Default consistency level for the sync and async clients is no longer "Session" and will instead be set to the
19
-
consistency level of the user's cosmos account setting on initialization if not passed during client initialization.
20
-
This change will impact client application in terms of RUs and latency. Users relying on default `Session` consistency will need to pass it explicitly if their account consistency is different than `Session`.
21
-
Please see [Consistency Levels in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/consistency-levels) for more details.
21
+
- Default consistency level for the sync and async clients is no longer `Session` and will instead be set to the
22
+
consistency level of the user's cosmos account setting on initialization if not passed during client initialization.
23
+
This change will impact client application in terms of RUs and latency. Users relying on default `Session` consistency
24
+
will need to pass it explicitly if their account consistency is different than `Session`.
25
+
Please see [Consistency Levels in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/consistency-levels) for more details.
22
26
- Fixed invalid request body being sent when passing in `serverScript` body parameter to replace operations for trigger, sproc and udf resources.
23
27
- Moved `is_system_key` logic in async client.
24
28
- Fixed TypeErrors not being thrown when passing in invalid connection retry policies to the client.
0 commit comments