[SERVER-73416] Index version not changed on collection after resharding Created: 27/Jan/23 Updated: 29/Oct/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2023-02-06 | ||||||||
| Participants: | |||||||||
| Description |
|
SERVER-70828 added functionality into resharding to copy the sharding index catalog if necessary, however, the index version must be bumped in order to inform the catalog about the change in the collection UUID. We could for example, use the same indexVersion in the temporary namespace, given the fact that after resharding is running, no new global indexes can be created or dropped due to the DDL coordinator for resharding. |
| Comments |
| Comment by Githook User [ 30/Jan/23 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |