[SERVER-58439] Analyze and mark references to encrypted fields in a find projection Created: 12/Jul/21 Updated: 06/Dec/22 Resolved: 17/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Optimization |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
As of v4.4, the projection spec of a find command can take expressive projections that may reference encrypted fields. The goal for this task is to walk the expression tree and detect any constants that should be marked for encryption, and fail on an invalid comparison/reference to an encrypted field. |