[SERVER-78510] Investigate whether $limit pushdown should be done for $vectorSearch Created: 28/Jun/23 Updated: 12/Jul/23 Resolved: 12/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alyssa Clark | Assignee: | Backlog - Query Integration |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm3294-m3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Participants: |
| Description |
|
Currently, we ensure that only candidates records are returned from DocumentSourceVectorSearch. We should revisit whether this is even necessary or if mongot can guarantee that it will only send back candidates records. Also, we should think about whether $limit pushdown is a worthwhile optimization to add. |
| Comments |
| Comment by Alyssa Clark [ 12/Jul/23 ] |
|
We are not going to implement $limit pushdown for $vectorSearch in this project. |