[SERVER-22402] Add dependency tracking to the $match stage Created: 01/Feb/16 Updated: 01/Aug/17 Resolved: 26/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Benjamin Murphy |
| Resolution: | Done | Votes: | 0 |
| Labels: | optimization | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Query 10 (02/22/16), Query 11 (03/14/16) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently DocumentSourceMatch does not implement getDependencies, which means that we cannot tell which fields will be needed by the match stage, and hence must ask for all fields. This can limit our ability to project out unneeded fields. We should add an implementation of getDependencies that will look at it's MatchExpression to determine which fields are needed. |
| Comments |
| Comment by Githook User [ 26/Feb/16 ] |
|
Author: {u'username': u'benjaminmurphy', u'name': u'Benjamin Murphy', u'email': u'benjamin_murphy@me.com'}Message: |