[MONGOCRYPT-66] Cache indicator that JSONSchema has no encrypted fields if schemaRequiresEncryption is false Created: 01/Apr/19  Updated: 27/Oct/23  Resolved: 25/May/19

Status: Closed
Project: Libmongocrypt
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Epic Link: Build libmongocrypt library

 Comments   
Comment by Kevin Albertson [ 25/May/19 ]

Per recent changes to the design, even if the json schema does not include encrypted fields, we must still run it through mongocryptd (to catch issues like $lookup on a separate encrypted collection). Since we can't optimize out sending to mongocryptd when schemaRequiresEncryption=false, there's no point of caching this.

Generated at Thu Feb 08 09:07:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.