[SERVER-65296] Add support for comparisons to encrypted fields under $project Created: 06/Apr/22 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Optimization
|
||||
| Participants: | |||||
| Description |
|
This ticket is to add server-side rewrite and query analysis support for comparisons to encrypted fields in $project. For example, we should allow the following simplistic pipeline: {$project: {isOneTwoThree: {$eq: ["$encryptedStr", "123"]}}} Also in this ticket we should consider adding support for references to encrypted fields in find projections. |