-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Fully Compatible
-
Execution Team 2020-03-23, Execution Team 2020-04-06
The following tasks need to be completed once we branch for 4.6:
1. Create a list of tickets with code and tests to remove, add them to the 4.6 Upgrade/Downgrade Epic, and mark them as "is depended on by" this ticket. This will assist the Upgrade/Downgrade team in tracking progress. If there is an insufficient amount of work to warrant multiple tickets, then the work can be done under this ticket directly.
2. Complete all necessary tickets promptly.
3. Update SERVER-46589, identifying Execution-related generic upgrade/downgrade references that the Upgrade/Downgrade team should update now that the 4.2-dependent references have been removed.
- depends on
-
SERVER-46773 Remove v4.4 FCV handling for simultaneous index builds
- Closed
-
SERVER-46777 Remove v4.4-specific handling for collection creation inside of transactions
- Closed
-
SERVER-46778 Remove v4.4 FCV handling for namespace length
- Closed
-
SERVER-46781 Remove v4.4 FCV handling for collection and index catalog entry 'ns' field
- Closed
-
SERVER-46782 Add a comment to FCV handling code in WiredTigerFileVersion::shouldDowngrade function to indicate that the FCV gating should be permanent across versions
- Closed
- related to
-
SERVER-46784 Make jstests/multiVersion/keystring_index.js a generic upgrade/downgrade test
- Closed