[SERVER-64632] Wider support for encrypted field references in aggregation Created: 18/Mar/22  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Optimization
Participants:

 Description   

Aside from basic equality, there are other spots in the aggregation grammar where a FLE-2 encrypted field could be referenced while giving correct query semantics.

1. Non-equality accumulator reference ($first, $last)
2. $push an encrypted field, but not $addToSet since it requires equality between randomly encrypted fields
3. Renaming an encrypted field (in aggregate pipeline, not update/findAndModify)
4. Branching/conditional expressions ($ifNull, $cond)


Generated at Thu Feb 08 06:00:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.