-
Type: Spec Change
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Client Side Encryption
-
Needed
-
Summary
- Document the purpose of trimFactor and sparsity.
- Make trimFactor and sparsity optional. Apply defaults chosen in
SERVER-91077in libmongocrypt. - Verify server default min/max values added in
SERVER-91075are applied client-side in libmongocrypt.
Motivation
trimFactor and sparsity are currently specified as required arguments in RangeOpts. trimFactor and sparsity are expected to be advanced configuration that most users would not know how to meaningfully change (see slack thread). Making them optional may ease usage. Documentation may help clarify that most users can leave these unset.
trimFactor is documented here:
- https://github.com/10gen/mongo/blob/master/src/mongo/db/modules/enterprise/docs/fle/fle_range.md#trim-factor
- https://docs.google.com/document/d/1099gEXs93NFtP6hNh_h5cIuKA05013Ll1hxPclVYyXo/edit#bookmark=id.lpqi4ys9xg3y
Is this issue urgent?
Yes. Should be done before Range GA (DRIVERS-2776).
- depends on
-
MONGOCRYPT-698 Make trimFactor and sparsity optional
- Closed
- split to
-
PHPC-2462 Document trimFactor and sparsity and make optional
- Closed
-
CXX-3071 Document trimFactor and sparsity and make optional
- Backlog
-
RUBY-3517 Document trimFactor and sparsity and make optional
- Backlog
-
CDRIVER-5636 Document trimFactor and sparsity and make optional
- Closed
-
CSHARP-5187 Document trimFactor and sparsity and make optional
- Closed
-
GODRIVER-3279 Document trimFactor and sparsity and make optional
- Closed
-
JAVA-5537 Document trimFactor and sparsity and make optional
- Closed
-
MOTOR-1341 Document trimFactor and sparsity and make optional
- Closed
-
NODE-6284 Document trimFactor and sparsity and make optional
- Closed
-
PYTHON-4566 Document trimFactor and sparsity and make optional
- Closed
-
RUST-1999 Document trimFactor and sparsity and make optional
- Closed