[SERVER-31346] Disallow 3.6 query features in view definitions when featureCompatibilityVersion=3.4 Created: 02/Oct/17  Updated: 30/Oct/23  Resolved: 20/Oct/17

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Querying
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: James Wahlin
Resolution: Fixed Votes: 0
Labels: read-only-views
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-10943 Disallow 3.6 query features in view d... Closed
Backwards Compatibility: Major Change
Sprint: Query 2017-10-23, Query 2017-11-13
Participants:

 Description   

When the featureCompatibilityVersion is 3.4, users should not be able to create a view that includes $expr or $jsonSchema in the $match stage. Disallowing this will prevent 3.4 secondaries from fasserting when replicating system.views and ensure that it is possible to downgrade to 3.4 as long as you have never set the featureCompatibilityVersion to 3.6.



 Comments   
Comment by Githook User [ 20/Oct/17 ]

Author:

{'email': 'james@mongodb.com', 'name': 'James Wahlin', 'username': 'jameswahlin'}

Message: SERVER-31346 Disallow 3.6 query features in views under FCV 3.4
Branch: master
https://github.com/mongodb/mongo/commit/02ecda9fcdc70eec55cf3ba80d22404fc681c0b1

Comment by David Storch [ 02/Oct/17 ]

In addition to the features mentioned in the description ($jsonSchema and $expr), this needs to be done for the $lookup-into-subpipeline syntax introduced in SERVER-29072. We should probably also brainstorm if there are any other smaller features which should be included here.

Generated at Thu Feb 08 04:26:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.