[SERVER-25304] Allow a MatchExpression to match a Document Created: 27/Jul/16 Updated: 30/Mar/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||
| Sprint: | Query 2019-09-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently the MatchExpression class has some methods to determine whether or not various types match the MatchExpression, but none of these are compatible with Document, which is used throughout the aggregation system. Instead of needing to convert from a Document to a BSONObj, it would be nice to directly apply the MatchExpression to the Document, and would likely result in performance gains. |
| Comments |
| Comment by David Storch [ 27/Sep/19 ] |
|
After a discussion with Pawel, we are removing this from the "single sort implementation" project. We should consider making a goal of the DocumentSource/PlanStage consolidation project instead. |
| Comment by David Storch [ 05/Sep/19 ] |
|
I will investigate the complexity/priority of this ticket during this sprint, based on the POC work done earlier by Misha. |