[DOCS-15219] Investigate changes in SERVER-63577: Ensure that new unique indexes don't have old format keys Created: 07/Apr/22 Updated: 13/Nov/23 Resolved: 20/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | release | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 15 weeks, 5 days ago | ||||||||
| Description |
|
Original Downstream Change Summary 5.0.7 and 5.3.2 will be the downgrade floor for 6.0. Earlier versions of 5.0.x and 5.3.x will not recognize the new unique index versions and would fail to start. Be sure to update the 6.0 Compatibility Notes with downgrade information. Description of Linked TicketWe can do this by introducing a new internal data format version and use that when creating new unique indexes. In the future, this new data format will guarantee that no legacy format secondary unique index entries are still around. |
| Comments |
| Comment by Kenneth Dyer [ 20/Oct/23 ] |
|
Work appears to've been done from a separate ticket. The 6.0 Compatibility page currently displays this information. |