[SERVER-67749] FLE2 Range Query: design: determine what are we doing as far as min/max/sparsity Created: 01/Jul/22  Updated: 28/Sep/22  Resolved: 28/Sep/22

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 6.1 Desired
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sergey Galtsev (Inactive) Assignee: Sergey Galtsev (Inactive)
Resolution: Done Votes: 0
Labels: FLE2, fle2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by MONGOCRYPT-482 Support double Closed
is depended on by SERVER-69666 FLE2 range float precision: investiga... Closed
is depended on by SERVER-69667 FLE2 range float precision: update ID... Closed
is depended on by SERVER-69668 FLE2 range float precision: update OS... Closed
is depended on by SERVER-69669 FLE2 range float precision: update Ed... Closed
is depended on by SERVER-69670 FLE2 range float precision: update mi... Closed
is depended on by SERVER-69671 FLE2 range float precision: update cr... Closed
Duplicate
is duplicated by SERVER-69666 FLE2 range float precision: investiga... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-09-19, Security 2022-10-03
Participants:

 Description   

There is an open question in design whether we allow min/max/sparsity parameters for non-integers


Generated at Thu Feb 08 06:08:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.