[SERVER-66327] Remove the setFeatureCompatibilityVersion code in the run_validate_collections.js hook Created: 09/May/22 Updated: 29/Oct/23 Resolved: 23/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.0-rc4 |
| Fix Version/s: | 6.0.0-rc8, 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||
| Sprint: | Execution Team 2022-05-30 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 31 | ||||||||||||
| Description |
|
This code was added in validate should no longer fail because of the server running with an FCV less than the latest version. There's also a build failure where the fuzzer creates a measurement index on a time-series collection and cannot complete a previously failed FCV downgrade, causing the hook to fail. |
| Comments |
| Comment by Githook User [ 24/May/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 23/May/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Max Hirschhorn [ 09/May/22 ] |
I'm confused about the "validate should no longer fail" part of this description. For some historical context, going back to decimal128 in MongoDB 3.4 ( As mentioned in this comment on SERVER-43627, if the validate command has the same behavior in both lower FCV and higher FCV then we can have the jstestfuzz*.yml files omit TestData.forceValidationWithFeatureCompatibilityVersion = latestFCV. |