[DOCS-12163] Update Operation Changes should be included in the features impacted by FCV Created: 26/Oct/18  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Arnie Listhaus Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

The Backwards Incompatible Features section in 3.6 should include the Update Operation Changes.

In the example below, you can see that setting FCV to 3.6 impacts the way data is stored when adding new fields to a document via an update statement.

> db.coll.drop()
true
> db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )
{ "ok" : 1 }
> db.coll.insert({ _id: 0, x: 0 })
WriteResult({ "nInserted" : 1 })
> db.coll.update({_id: 0}, {$set: {b: 0, a: 0}})
WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 })
> db.coll.find()
{ "_id" : 0, "x" : 0, "b" : 0, "a" : 0 }

Note: when FCV is set to 3.4, fields are added in the order they were presented

> db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )
{ "ok" : 1 }
> db.coll.update({_id: 0}, {$set: {d: 0, c: 0}})
WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 1 })
> db.coll.find()
{ "_id" : 0, "x" : 0, "b" : 0, "a" : 0, "c" : 0, "d" : 0 }

Note: when FCV is set to 3.6, fields are added in lexicographic order

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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