[SERVER-44233] Remove checking that shardVersion UNSHARDED was sent from database_and_shard_versioning_all_commands.js Created: 24/Oct/19 Updated: 29/Oct/23 Resolved: 25/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-11-04 |
| Participants: |
| Description |
|
The test is quite bloated, and one way to streamline it is to remove checking that shardVersion UNSHARDED is sent. This check is not that useful anyway, because it relies on the UNSHARDED shardVersion showing up in the profiler, which doesn't work for many commands and the test has to specify which commands this method works for. |
| Comments |
| Comment by Githook User [ 25/Oct/19 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |
| Comment by Githook User [ 24/Oct/19 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |