[SERVER-70413] Let crypto code deal with optional min/max Created: 10/Oct/22  Updated: 05/Dec/22  Resolved: 02/Nov/22

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

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

Assigned Teams:
Query Optimization
Participants:

 Description   

Right now the FLE2RangeFindSpec mandates non-optional min/max for the encrypted index, when the crypto code can in fact handle optional values for these fields. This ticket should:
1. Make the fields optional
2. add the indexType to the find spec
3. Update code to handle optional types and propagate optional from the encrypted field config.


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