-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.