[SERVER-69769] Add `keyPattern` to all range deletion documents missing it on upgrade to v8.0 Created: 16/Sep/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | 7.0UpDown, oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Implement an upgrade procedure to populate range deletion task document with the key pattern. This is a necessary step to simplify the shard key pattern retrieval starting from v8.1, as it will be guaranteed that no range deletion task document are written down without the key pattern field (hence, no refreshes will be needed). It will not be necessary to delete the field on downgrade as keeping it doesn't harm: the parsing of range deletion documents is not strict and the field will be simply ignored. |
| Comments |
| Comment by Silvia Surroca [ 05/Oct/22 ] |
|
This ticket will be posponed to v8.0 since that change may imply a considerable increment in the upgrade time duration, especially when the upgrade comes from a release lower that v6.2 (where the `keyPattern` field is still not set on the new range deletion documents). |