[DOCS-13320] Investigate changes in SERVER-42421: Plug in BSON -> ProjectionAST parser to find command path Created: 02/Jan/20  Updated: 13/Nov/23  Due: 05/Jun/20  Resolved: 04/Jun/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: docs-query
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-42421 Plug in BSON -> ProjectionAST parser ... Closed
Related
Participants:
Days since reply: 3 years, 35 weeks, 6 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

There were a number of small changes to the projection language made by this ticket:

1) Projecting on top-level dollar prefixed fields in find() is now banned, with a few exceptions ($sortKey, $recordId, for example) that are for internal use by mongos.
Example:

db.c.find({a: 1}, {$foobar: 1}) // Now illegal

2) Performing a projection on a field that also has the $slice expression applied to it is illegal.
Example:

db.c.find({}, {“comments”: {$slice: 1}, “comments.id”: 1}) // Illegal

3) $slice may not be used with positional projection on the same field.
Example:

db.c.find({"x.a": 1}, {"x.$": {$slice: -1}}) // Illegal

4) It is now illegal to project an empty field name

Description of Linked Ticket

null

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 04/Jun/20 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13320: find projection restrictions
Branch: master
https://github.com/mongodb/docs/commit/08a1cd78cc799d7c005bfb2bd9a0c761cb3fb269

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