[SERVER-42418] Allow ExpressionMeta to parse find() $meta options Created: 25/Jul/19 Updated: 29/Oct/23 Resolved: 21/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Query 2019-08-26 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Add support for "recordId" "indexKey" and "sortKey" in ExpressionMeta. Like other meta types, the expression should returning "missing" if the associated metadata cannot be found on the Document. This ticket will also involve modifying Document and DocumentMetadataFields. The main purpose of this work is to make ExpressionMeta supercede find() $meta. Note that the work of figuring out how to pass metadata between the PlanStage and DocumentSource layer is tracked by |
| Comments |
| Comment by Ian Boros [ 03/Sep/19 ] |
|
Yep! Is there already a docs ticket about that? |
| Comment by Githook User [ 21/Aug/19 ] |
|
Author: {'username': 'puppyofkosh', 'email': 'ian.boros@mongodb.com', 'name': 'Ian Boros'}Message: |
| Comment by Ian Boros [ 25/Jul/19 ] |
|
Please talk to me before starting this. |