[SERVER-41337] [FLE] Handle encrypted-prefix field paths and ExpressionObject in agg expression analysis Created: 28/May/19  Updated: 06/Dec/22  Resolved: 03/Nov/22

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Backlog - Query Optimization
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-41807 [FLE] Add merge operation for Encrypt... Backlog
is depended on by SERVER-41331 [FLE] Add support for ROOT and CURREN... Closed
Duplicate
is duplicated by SERVER-41334 [FLE] Support object expressions in s... Closed
Related
is related to SERVER-41716 [FLE] Support comparing an encrypted ... Backlog
Assigned Teams:
Query Optimization
Sprint: Query 2019-06-17
Participants:

 Comments   
Comment by Jacob Evans [ 03/Nov/22 ]

Closing this since FLE 2 does not support objects, including those partially encrypted as referred to by an encrypted prefix.

Comment by Nicholas Zolnierz [ 07/Jun/19 ]

ted.tuckman I've retitled this ticket based on our recent discussions. SERVER-41335 handles changes the schema walker while this ticket will handle replacement of encrypted fields involving prefixes and ExpressionObjects. I'm not sure if it already works this way, but we should also make sure that objects/prefixes with encrypted fields correctly fail in an evaluated subtree. For example:

 
{$gt: [$prefixOfEncrypted,{someField: 1}]}

Generated at Thu Feb 08 04:57:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.