[SERVER-38760] Add the ability to serialize an update back to BSON which means the same thing Created: 21/Dec/18 Updated: 29/Oct/23 Resolved: 28/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Jacob Evans |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Query 2019-02-11, Query 2019-02-25, Query 2019-03-11 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 70 | ||||||||||||||||||||
| Description |
|
Both MatchExpression and all aggregation stages have this ability. We also want it on the update stage - though this will likely be harder since an update represents itself as a tree of nodes which may not look quite the same as the original document. |
| Comments |
| Comment by Githook User [ 28/Feb/19 ] |
|
Author: {'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}Message: |
| Comment by Githook User [ 28/Feb/19 ] |
|
Author: {'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}Message: |
| Comment by Githook User [ 28/Feb/19 ] |
|
Author: {'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}Message: |
| Comment by Nicholas Zolnierz [ 28/Jan/19 ] |
|
jacob.evans - it may make sense to split out array filters as a separate ticket. I imagine we'll at least need a method for serializing the positional element in the update expression but the arrayFilters BSON can just pass through to the serialized command object. What're your thoughts? |