[SERVER-67454] Migrate printShardingStatus shell helper logic to database command Created: 22/Jun/22 Updated: 12/Dec/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alex Bevilacqua | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | 12/12 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
The sh.status() and db.printShardingStatus() shell helpers both call the getPrintableShardingStatus mongosh function. Exposing those intermediate commands would allow customer to retrieve this information more easily also from other drivers (aka outside of the mongosh) |
| Comments |
| Comment by Garaudy Etienne [ 18/Jul/22 ] |
|
lamont.nelson@mongodb.com let's talk about it at product sync |
| Comment by Lamont Nelson [ 15/Jul/22 ] |
|
garaudy.etienne@mongodb.com pinging you here to draw your attention. We think the question is whether we want to do this as a command or not. Would it be valuable? |