This change relaxes a restriction on the server & query analysis code when validating a queryable encryption schema ("encryptedFieldConfig") that defines range-indexed encrypted fields. Specifically, the min and max fields are no longer required for int, long, and date types, and the sparsity field is no longer required for all types. For int, an unspecified min implies a default lower bound of -1 * 2^31 (or -2147483648) and an unspecified max implies a default upper bound of 2^31 - 1 (or 2147483647). For long, the implicit default min and max are (-1 * 2^63) and (2^63 - 1) respectively. In terms of milliseconds since the Unix epoch, date has the same default implicit upper and lower bounds as long. Sparsity currently defaults to a value of 1, but this is not final, and is expected to be changed in SERVER-91077.

Description of Linked Ticket

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.