Both MatchExpression and all aggregation stages have this ability. We also want it on the update stage - though this will likely be harder since an update represents itself as a tree of nodes which may not look quite the same as the original document.
- is depended on by
-
SERVER-39253 [FLE] Handle $set to an object with encrypted fields
- Closed
-
SERVER-39254 [FLE] Reject $rename operations between encrypted fields
- Closed
-
SERVER-39257 [FLE] Handle encrypted field in $set
- Closed
-
SERVER-39276 [FLE] Reject invalid update operators on encrypted fields
- Closed