[SERVER-66096] Fix too strict config DB name assertion in catalog shard POC Created: 29/Apr/22 Updated: 29/Oct/23 Resolved: 04/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | Andrew Shuvalov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The `ShardConfig::_runCommand()` arg `dbName` is not necessary 'config' or 'admin'. Example: ConfigsvrCollModCommand. Narrow the assertion 6485501. |