Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
If the documentation team doesn't think that this will clutter the documentation, it would be nice if we could document for versions of the databases <= 4.4 operators which act on multiple paths will act on them in lexographic order (so "a.10" before "a.2"). In the future ,these updates will happen in numeric order if a path component is entirely composed of numbers (so "a.2" before "a.10").
Scope of changes
I think we'll want to update:
- https://docs.mongodb.com/v4.4/reference/operator/update/
- https://docs.mongodb.com/manual/release-notes/5.0-compatibility/
Maybe also consider a note/include to be added to the Behavior section of affected update operators:
- https://docs.mongodb.com/v4.4/reference/operator/update/rename/#mongodb-update-up.-rename/#behavior
- https://docs.mongodb.com/v4.4/reference/operator/update/pop/#behavior
- https://docs.mongodb.com/v4.4/reference/operator/update/bit/#mongodb-update-up.-bit
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-50778 "Cannot apply $bit" when $bit update grows an array
-
- Closed
-
- related to
-
DOCS-14795 DOCS-14795 Document update order for update operators that act on multiple paths act in numeric order for versions >= 5.0
-
- Closed
-