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.