[DOCS-12504] Warn that documents with duplicate key names are not supported Created: 22/Feb/19 Updated: 30/Oct/23 Resolved: 10/Sep/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Nathan Contino (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | docs-onboarding-candidate | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 4 years, 22 weeks, 1 day ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
DescriptionLow level BSON helpers in some drivers (for example, the BSON writer in the Java driver) can be abused to create documents with duplicate key names. For example:
The BSON spec is silent on the issue of duplicate key names. The server's behavior when confronted with duplicate key names is undefined. Since drivers generally use a map to represent a BSON document, only one of the keys will survive decoding and reinsertion of such a document. A good place to add this might be https://docs.mongodb.com/manual/reference/limits/#Restrictions-on-Field-Names but the text should really be a warning / call to action. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 10/Sep/19 ] |
|
Author: {'name': 'nathan-contino-mongo', 'username': 'nathan-contino-mongo', 'email': 'nathan.contino@mongodb.com'}Message: |