[SERVER-76976] Programmatic API to get information on sharded collections Created: 10/May/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
Some functionalities of the drivers and Mongo Shell require access to information on the shared collections. Such information is persisted in the config database owned by the Config Server. Commands, like db.collection.getShardDistribution(), are currently implemented by accessing directly to these config collections, which requires to be aware of implementation details that could change from one version to another of the server. The idea is to decouple these command implementations from the internal representation of the system collections by exposing a programmatic API. Such API can be used to retrieve information on sharded collections, ensuring support and consistency regardless the internal representation of this information. |
| Comments |
| Comment by Kaloian Manassiev [ 10/May/23 ] |
|
It is not urgent at all. Title |
| Comment by Kaloian Manassiev [ 10/May/23 ] |
|
This looks like something that might need a Scope and sign-off from the downstream teams. So it is probably better suited to be a mini-project. CC cris.insignarescuello@mongodb.com: Should we convert this into a mini-Epic? |