[SERVER-44825] Add coverage for range deletions with refine shard key Created: 25/Nov/19 Updated: 29/Oct/23 Resolved: 10/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (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 2020-02-10, Sharding 2020-02-24 |
| Participants: |
| Description |
|
We should test cases where range deletions are currently enqueued for a collection whose shard key is then refined before the range deletion is processed by the range deleter. It should still delete the range since the bounds will be the same. |
| Comments |
| Comment by Githook User [ 10/Feb/20 ] |
|
Author: {'name': 'Matthew Saltz', 'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com'}Message: create mode 100644 jstests/sharding/range_deleter_interacts_correctly_with_refine_shard_key.js |