[SERVER-34456] Add comprehensive testing for KeyString length decoding Created: 13/Apr/18 Updated: 29/Oct/23 Resolved: 11/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Neha Khatri | Assignee: | Neha Khatri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage Non-NYC 2018-04-23, Storage Non-NYC 2018-05-07, Storage Non-NYC 2018-05-21 |
| Participants: | |
| Story Points: | 5 |
| Description |
|
Unique index key format would be changed to enable PIT reads from secondary. As a result, unique indexes could have both old and new format keys after an upgrade. Reading keys from mixed format index requires distinguishing old and new format keys. This ticket aims to add comprehensive test for this new KeyString length decoding function. |
| Comments |
| Comment by Githook User [ 10/May/18 ] |
|
Author: {'name': 'nehakhatri5', 'email': 'neha.khatri@mongodb.com', 'username': 'nehakhatri5'}Message: |