[SERVER-81967] Rely only on `getDatabaseVersion` to get the cached database version from MongoS Created: 08/Oct/23 Updated: 20/Oct/23 |
|
| Status: | Open |
| 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: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
The `getShardVersion` command exposed by the MongoS can be used to get the cached version of a given database. Nevertheless, in the context of the MongoS interface parity initiative, starting from version 7.1, the MongoS also exposes the `getDatabaseVersion` command ( The goal of this ticket is to get rid from tests of the use of the `getShardVersion` command and rely only on `getDatabaseVersion` to get the cached database version from both MongoS and MongoD (interface parity). This can be implemented once version 8.0 becomes last LTS. |