Azure · analogrelay · May 28, 2026 · May 20, 2026 · May 20, 2026 · May 20, 2026
diff --git a/Cargo.lock b/Cargo.lock
@@ -88,6 +88,7 @@ async-stream = { version = "0.3.6" }
 async-trait = "0.1"
 base64 = "0.22"
 arc-swap = "1.7"
+backtrace = "0.3"
 bytes = "1.11.1"
 cargo_metadata = "0.23.1"
 clap = { version = "4.5.58", features = ["derive"] }

@@ -57,6 +57,7 @@
     "fabianm",
     "failback",
     "failovers",
+    "fanout",
     "FILETIME",
     "flamegraph",
     "fmix",
@@ -154,6 +155,7 @@
     "southindia",
     "sproc",
     "sprocs",
+    "stdlib",
     "subsec",
     "substatus",
     "supportedcapabilities",

@@ -226,7 +226,7 @@ If a separate builder type is used, follow these conventions:
 1. Name it `<Type>Builder`.
 2. Keep builder fields private.
 3. Provide `with_*` setters for optional fields.
-4. Provide terminal `build(self, ...) -> <Type>` (or `azure_core::Result<Type>` when fallible).
+4. Provide terminal `build(self, ...) -> <Type>` (or `crate::error::Result<Type>` / `azure_data_cosmos::Result<Type>` when fallible).
 5. Keep required fields on `build(...)`, not as optional builder state.
 6. Add `<Type>::builder(... required args ...) -> <Type>Builder` to initialize the builder type.
 

@@ -45,7 +45,7 @@ impl MyType {
 
 // ✅ GOOD: Implement the standard trait
 impl std::str::FromStr for MyType {
-    type Err = azure_core::Error;
+    type Err = azure_data_cosmos::Error;
     fn from_str(s: &str) -> Result<Self, Self::Err> { /* ... */ }
 }
 
@@ -66,7 +66,7 @@ If you need a non-fallible parse internally, create a **private** helper method
 
 #### Error Handling
 
-- Use `azure_core::Result<T>` for all fallible operations
+- Use `azure_data_cosmos::Result<T>` (SDK) or `azure_data_cosmos_driver::error::Result<T>` (driver) for all fallible operations — both alias `Result<T, crate::Error>` over the typed Cosmos error.
 - **Prefer returning `Result::Err` over panicking** in public methods whose inputs could originate from user-constructed types (even indirectly). Callers can then decide whether to propagate, log, or handle — rather than crashing their application. Use `assert!`/`panic!` only for true invariant violations that indicate programmer error in internal code.
 - Cosmos-specific errors should provide:
   - HTTP status code
@@ -190,7 +190,7 @@ pub async fn create_item<T: Serialize>(
     &self,
     item: &T,
     options: &CreateItemOptions,
-) -> azure_core::Result<ItemResponse<T>>
+) -> azure_data_cosmos::Result<ItemResponse<T>>
 where
     T: for<'de> Deserialize<'de>,
 {
@@ -355,7 +355,7 @@ pub mod builders {
             endpoint: impl Into<String>,
             credential: impl TokenCredential,
             options: DriverOptions,
-        ) -> azure_core::Result<Driver> {
+        ) -> azure_data_cosmos_driver::error::Result<Driver> {
             // ... construction logic
         }
     }

@@ -4,7 +4,9 @@
 
 ### Features Added
 
-- Added `RegionStrategy::PreferredRegions` to allow specifying a fixed region preference order for failover, hedging, and retry. ([#4485](https://github.com/Azure/azure-sdk-for-rust/pull/4485))
+- `CosmosError` can capture a stack backtrace on construction. Capture is opt-in (off by default; on when `RUST_BACKTRACE` is set or when explicit capacities are supplied) and protected against error storms by two configurable per-second limiters on the runtime builder. ([#4442](https://github.com/Azure/azure-sdk-for-rust/pull/4442))
+- Introduced `azure_data_cosmos::CosmosError` and the crate-wide `azure_data_cosmos::Result<T>` alias, surfacing typed `CosmosStatus` (with predicate accessors like `is_not_found()` / `is_throttled()` / `is_transient()`), the originating `CosmosResponse`, and the operation `DiagnosticsContext` on every failure. `From<CosmosError> for azure_core::Error` is provided so callers using `?` against `azure_core::Error` continue to compose. ([#4442](https://github.com/Azure/azure-sdk-for-rust/pull/4442))
+- Added `RoutingStrategy::PreferredRegions` to allow specifying a fixed region preference order for failover, hedging, and retry. ([#4485](https://github.com/Azure/azure-sdk-for-rust/pull/4485))
 - Standardized every client-method options type with a public `operation: OperationOptions` field and `with_operation_options(OperationOptions) -> Self` setter, so any per-request `OperationOptions` setting can be configured via any options type. The following options types previously had no way to attach `OperationOptions` and now do: `ReadContainerOptions`, `ReadDatabaseOptions`, `ReplaceContainerOptions`, `CreateContainerOptions`, `CreateDatabaseOptions`, `DeleteContainerOptions`, `DeleteDatabaseOptions`, `QueryContainersOptions`, `QueryDatabasesOptions`, `ThroughputOptions`, `ReadFeedRangesOptions`. For `CreateContainerOptions` / `CreateDatabaseOptions` / `ReplaceContainerOptions`, the SDK still forces `content_response_on_write = Enabled` on the resolved options because control-plane mutations require the response body. `ReadFeedRangesOptions::operation` is currently inert (the underlying routing-map cache does not go through the operation pipeline) but is added for shape consistency with the other options types.
 - Added `new()` constructors and `with_x` consuming setters to multi-required-field model types so callers can build them declaratively without struct-literal syntax (which is now blocked by `#[non_exhaustive]`): `VectorEmbedding::new(path, data_type, dimensions, distance_function)` + `with_path` / `with_data_type` / `with_dimensions` / `with_distance_function`; `ConflictResolutionPolicy::new(mode)` + `with_resolution_path` / `with_resolution_procedure`; `SpatialIndex::new(path)` + `with_type` (singular pusher onto `types`); `CompositeIndexProperty::new(path, order)` + `with_path` / `with_order`; `VectorIndex::new(path, index_type)` + `with_path` / `with_index_type`. These types do **not** implement `Default` — their constructors require values that have no meaningful default.
 - Derived `Default` on `VectorEmbeddingPolicy`, `UniqueKeyPolicy`, `UniqueKey`, `PropertyPath`, and `CompositeIndex`, and added singular `with_x` pushers / setters: `VectorEmbeddingPolicy::with_embedding`, `UniqueKeyPolicy::with_unique_key`, `UniqueKey::with_path`, `PropertyPath::with_path`, and `CompositeIndex::with_property`. This matches the existing `IndexingPolicy::with_included_path` style and lets callers build these policies declaratively without constructing intermediate `Vec`s.
@@ -17,6 +19,7 @@
 
 ### Breaking Changes
 
+- All fallible public APIs now return `azure_data_cosmos::Result<T>` (= `Result<T, CosmosError>`) instead of `azure_core::Result<T>`, and the error type was renamed `Error` → `CosmosError` (with `CosmosErrorBuilder` for construction). Categorization moved from a `Kind` enum to predicates on `CosmosStatus` (`is_not_found()`, `is_throttled()`, `is_transient()`, …); the underlying `azure_core::Error` is still reachable via `std::error::Error::source()`. ([#4442](https://github.com/Azure/azure-sdk-for-rust/pull/4442))
 - Moved `QueryOptions::max_item_count` and `QueryOptions::continuation_token` into the new `QueryOptions::feed: FeedOptions` field. Callers that read or assign these fields directly should switch to `options.feed.max_item_count` / `options.feed.continuation_token`. The `with_max_item_count` / `with_continuation_token` convenience setters on `QueryOptions` continue to work unchanged.
 - `ThroughputProperties` is now `#[non_exhaustive]` and no longer derives `Default`. The `Default` impl produced a meaningless wire payload (no manual throughput and no autoscale settings, which would send an empty offer body). Callers should use `ThroughputProperties::manual(throughput)` or `ThroughputProperties::autoscale(starting_maximum_throughput, increment_percent)` instead.
 - Marked the following public model enums and response wrappers as `#[non_exhaustive]` to allow future variants/fields to be added without further breaking changes: `VectorDataType`, `VectorDistanceFunction`, `ConflictResolutionMode`, `IndexingMode`, `SpatialType`, `CompositeIndexOrder`, `VectorIndexType`, `BatchResponse`, `ItemResponse`, `ResourceResponse<T>`, `ResponseBody`, `ResponseHeaders`, `PartitionKeyVersion` and `CosmosStatus`. Callers must use `..` wildcard arms in `match`es over these enums and cannot construct these structs via struct-literal syntax (the SDK already provides constructors / setters for the constructable types).
@@ -43,7 +46,6 @@
 - Removed `azure_data_cosmos::constants::SubStatusCode` and its `new`/`value`/`from_header_value`/`From`/`Display`/`Debug` API. The SDK no longer maintains a parallel sub-status-code type.
 - The `User-Agent` header on every outgoing Cosmos DB request now identifies the wrapping SDK in addition to the driver. The new format is `azsdk-rust-cosmos/<sdk-version> azsdk-rust-cosmos-driver/<driver-version> <os>/<arch> rustc/<ver> [suffix]`, where `<sdk-version>` is this crate's version. This is wired automatically via the new `CosmosDriverRuntimeBuilder::with_wrapping_sdk_identifier` API in the driver, and lets telemetry distinguish callers using `azure_data_cosmos` from callers driving `azure_data_cosmos_driver` directly. No API surface in `azure_data_cosmos` changes. ([#4465](https://github.com/Azure/azure-sdk-for-rust/pull/4465))
 - The `azure_data_cosmos::constants` module is no longer public. It only contained internal HTTP-header-name constants used by the SDK's own pipeline plumbing; nothing from it was intended for consumer use. The one previously-exposed public item (`SubStatusCode`) is re-exported from the crate root — see the bullet above.
->>>>>>> Conflict 1 of 1 ends
 
 ### Bugs Fixed
 

@@ -933,10 +933,11 @@ ContainerConfig::new()
 
 `with_partition_count` and `with_throughput` are infallible setters; all
 validation happens in a single `build()` step that returns
-`azure_core::Result<ContainerConfig>`. Use `build()?` inside a function
-that returns `azure_core::Result<_>` (or `unwrap()` in tests).
+`azure_data_cosmos_driver::error::Result<ContainerConfig>`. Use `build()?`
+inside a function that returns a compatible `Result<_, _>` (or `unwrap()`
+in tests).
 
-Minimum provisioned throughput is 400 RU/s; values below this and a partition count of `0` are rejected with an `azure_core::Error` from `build()`.
+Minimum provisioned throughput is 400 RU/s; values below this and a partition count of `0` are rejected with a `Client`-kind `azure_data_cosmos_driver::error::Error` from `build()`.
 
 ### Per-Partition Tracking
 

@@ -3,7 +3,6 @@
 
 use std::error::Error;
 
-use azure_core::http::StatusCode;
 use azure_data_cosmos::CosmosClient;
 use clap::{Args, Subcommand};
 
@@ -65,7 +64,7 @@ impl DeleteCommand {
                     .delete_item(partition_key, &item_id, None)
                     .await;
                 match response {
-                    Err(e) if e.http_status() == Some(StatusCode::NotFound) => {
+                    Err(e) if e.status().is_not_found() => {
                         println!("Item not found!")
                     }
                     Ok(_) => println!("Item deleted"),

@@ -3,7 +3,6 @@
 
 use std::error::Error;
 
-use azure_core::http::StatusCode;
 use azure_data_cosmos::CosmosClient;
 use clap::{Args, Subcommand};
 
@@ -60,7 +59,7 @@ impl ReadCommand {
                     .read_item(&partition_key, &item_id, None)
                     .await;
                 match response {
-                    Err(e) if e.http_status() == Some(StatusCode::NotFound) => {
+                    Err(e) if e.status().is_not_found() => {
                         println!("Item not found!")
                     }
                     Ok(r) => {

@@ -3,7 +3,6 @@
 
 use std::error::Error;
 
-use azure_core::http::StatusCode;
 use azure_data_cosmos::{
     ContentResponseOnWrite, CosmosClient, ItemWriteOptions, OperationOptions, PartitionKey,
 };
@@ -91,7 +90,7 @@ impl ReplaceCommand {
                     .replace_item(pk, &item_id, item, options)
                     .await;
                 match response {
-                    Err(e) if e.http_status() == Some(StatusCode::NotFound) => {
+                    Err(e) if e.status().is_not_found() => {
                         println!("Item not found!")
                     }
                     Ok(r) => {

@@ -45,11 +45,15 @@ impl AccountEndpoint {
 }
 
 impl std::str::FromStr for AccountEndpoint {
-    type Err = azure_core::Error;
+    type Err = crate::CosmosError;
 
     fn from_str(s: &str) -> Result<Self, Self::Err> {
         let url: Url = s.parse().map_err(|e: url::ParseError| {
-            azure_core::Error::new(azure_core::error::ErrorKind::Other, e)
+            crate::DriverCosmosError::builder()
+                .with_status(crate::CosmosStatus::CLIENT_INVALID_ACCOUNT_ENDPOINT_URL)
+                .with_message("invalid account endpoint URL")
+                .with_arc_source(std::sync::Arc::new(e))
+                .build()
         })?;
         Ok(Self(url))
     }

@@ -14,7 +14,7 @@ use std::sync::Arc;
 ///
 /// This type bundles together the account endpoint and the credential needed to
 /// authenticate with it. Use convenience constructors [`with_credential()`](Self::with_credential)
-/// or [`with_authentication_key()`](Self::with_authentication_key) to create instances.
+/// or [`with_authentication_key()`](Self::with_authentication_key) (requires the `key_auth` feature) to create instances.
 ///
 /// # Examples
 ///