[SERVER-28706] Merge Aggregation Pipeline and CRUD Operations into a Single Query Pipeline Created: 10/Apr/17 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mohannad Saeed | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
Instead of having commands for finding, creating, updating, and deleting documents and also a pipeline for aggregating documents, why do not we have a single pipeline where one can also add $create, $update, $delete stages and we call this generic pipeline Query Pipeline? This will give powerful query expressions such as create, updating, or deleting based on previous stages results. Also, it will shift a lot of application layer logic to database layer. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 17/Apr/17 ] |
|
Hey Mohannad, this is definitely something that we are working towards though you won't necessarily see much activity on this particular ticket because we're still in the planning and prioritization phases and the work involved here will likely span many tickets. |