-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Queryable Encryption
-
Server Security
-
Minor Change
-
ALL
-
v8.0
-
Security 2024-06-10, Security 2024-06-24
The IDL validator for the EncryptedFieldConfig enforces a requirement that the min and max fields must be specified for range query specs for types int, long, and date. In addition, sparsity must be specified for all range types. The crypto team has asked that we make the min, max, and sparsity fields optional.
For int & long long, query analysis will default to using std::numeric_limits<T>::min() and std::numeric_limits<T>::max() for unspecified min & max, respectively, when setting the min/max in the FLE2RangeInsertSpec or in the FLE2RangeFindSpecEdgesInfo. For date, the default min is Date_t::min() and default max is Date_t::max(). Sparsity will default to 1.
- is depended on by
-
MONGOCRYPT-698 Make trimFactor and sparsity optional
- Closed
-
COMPASS-8013 Investigate changes in SERVER-91075: Make min, max, and sparsity optional when validating a QE range QueryTypeConfig
- Closed