[SERVER-46427] collection validator FCV test should not expect startup to fail Created: 26/Feb/20  Updated: 29/Oct/23  Resolved: 27/Feb/20

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2020-03-09
Participants:
Linked BF Score: 38

 Description   

Since SERVER-45611 got merged into 4.2, collection_validator_feature_compatibility_version.js has started failing. The test expects start up of a last-stable mongod to fail when there is a collection validator using new query features present. We should change the test to instead check that inserts fail.



 Comments   
Comment by Githook User [ 27/Feb/20 ]

Author:

{'name': 'Ian Boros', 'username': 'puppyofkosh', 'email': 'ian.boros@mongodb.com'}

Message: SERVER-46427 update FCV test to account for lazy checking of collection validators
Branch: master
https://github.com/mongodb/mongo/commit/edeec8b8fa426055735fd72b4149f56b70ca5eff

Generated at Thu Feb 08 05:11:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.