[SERVER-40627] [FLE] Ban schemas which define a deterministic encrypted field without an explicit single encrypt.bsonType Created: 12/Apr/19  Updated: 29/Oct/23  Resolved: 30/Apr/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Ted Tuckman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query 2019-04-22, Query 2019-05-06
Participants:

 Description   

In addition to the restrictions specified in SERVER-40516 (can't encrypt single-valued types), we also need to ban bsonType "object" since we can't guarantee correctness in equality queries. This ticket should change the parser on both mongod as well as mongocryptd.



 Comments   
Comment by Githook User [ 30/Apr/19 ]

Author:

{'email': 'ted.tuckman@mongodb.com', 'name': 'Ted Tuckman', 'username': 'TedTuckman'}

Message: SERVER-40627 Require exactly one bsonType for deterministic encryption
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/b7c4ab8ed28ff5297fce7a49d5dbb42069fef525

Comment by Githook User [ 30/Apr/19 ]

Author:

{'name': 'Ted Tuckman', 'username': 'TedTuckman', 'email': 'ted.tuckman@mongodb.com'}

Message: SERVER-40627 Ban schemas which define a deterministic encrypted field without an explicit single encrypt.bsonType
Branch: master
https://github.com/mongodb/mongo/commit/f7a4c4a9632f75996ed607ffc77e2a3cab15ea88

Generated at Thu Feb 08 04:55:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.