[DOCS-10622] Minor changes to update behavior in 3.6 Created: 02/Aug/17 Updated: 30/Oct/23 Resolved: 23/Oct/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Kevin Albertson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 16 weeks, 2 days ago |
| Epic Link: | DOCS: 3.6 Server |
| Story Points: | 1 |
| Description |
|
In MongoDB 3.6, when the featureCompatibilityVersion is 3.6, we use our new update system implementation, which supports arrayFilters. This system has some minor behavior differences from 3.4 that may be worth documenting in the release notes:
I will leave it to the discretion of the docs team which behavior changes are worth documenting. If you have any concerns about a backwards-breaking change, or any questions, feel free to reach out. |
| Comments |
| Comment by Githook User [ 23/Oct/17 ] | ||
|
Author: {'email': 'kevin.albertson@10gen.com', 'name': 'Kevin Albertson', 'username': 'kevinAlbs'}Message: | ||
| Comment by Kevin Albertson [ 20/Oct/17 ] | ||
|
Thanks Charlie. As it happens:
doesn't work because the shell does some validation.
does work. I'll document this behavior. | ||
| Comment by Charlie Swanson [ 20/Oct/17 ] | ||
|
kevin.albertson it is possible if it is inserted as a field name within a nested document. Our field validation only checks top-level fields I think, though we document that any $-prefixed field name is disallowed. | ||
| Comment by Kevin Albertson [ 19/Oct/17 ] | ||
|
tess.avitabile Is it possible to insert a document with the key "$[]"? I was unable to in 3.4 and 3.6. |