Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support preferred locations for Cosmos DB connections #2290

Open
rwincewicz-alianza opened this issue Mar 6, 2025 · 0 comments
Open

Support preferred locations for Cosmos DB connections #2290

rwincewicz-alianza opened this issue Mar 6, 2025 · 0 comments
Assignees
Labels
Cosmos The azure_cosmos crate customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team

Comments

@rwincewicz-alianza
Copy link

Feature Summary

Include an option for CosmosClient where you can provide a list of preferred locations, similar to the Cosmos DB Python SDK

Feature Description

At the moment there's no way of indicating which region you want a database request to go to, you just provide the global URL when you create the CosmosClient instance. In cases where you are using multiple regions for redundancy this might not matter because you only need to use a satellite region if the primary one is unavailable. In cases where you have multiple regions to reduce latency it's key that you can direct requests to a specific region.

The Cosmos DB Python SDK has a feature that does this documented here and I expect the Rust equivalent would work in a similar way.

Use Case

No response

Alternatives

An alternative approach is to use the region-specific URL but this doesn't work for satellite regions, see separate bug report.

Additional Context

No response

@github-project-automation github-project-automation bot moved this to Untriaged in Azure SDK Rust Mar 6, 2025
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Mar 6, 2025
@RickWinter RickWinter added the Cosmos The azure_cosmos crate label Mar 6, 2025
@github-actions github-actions bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 6, 2025
@analogrelay analogrelay self-assigned this Mar 6, 2025
@analogrelay analogrelay added feature-request This issue requires a new behavior in the product in order be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Mar 6, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Mar 6, 2025
@RickWinter RickWinter removed the feature-request This issue requires a new behavior in the product in order be resolved. label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cosmos The azure_cosmos crate customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Development

No branches or pull requests

3 participants