[DOCS-12676] Docs for SERVER-39258: Handle non-simple collation in commands sent to mongocryptd Created: 03/May/19  Updated: 13/Nov/23  Resolved: 31/Jul/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.11, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: docs-4.2-client-side-encryption
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-39258 Handle non-simple collation in comman... Closed
Duplicate
Participants:
Days since reply: 4 years, 28 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

We can choose to document that mongocryptd will detect when executing a command would require a collation-aware comparison to a string field. However, mongocryptd can only detect an error in this situation when the collation is passed explicitly with the query. Collection-default collations are unknown to mongocryptd, and cannot be supported in the same way. For details, see the query support document for FLE: https://docs.google.com/document/d/1r8jB7qr25UPW76-EFyR7DQsZ2ApPcRxGTRrFpBErsa4/edit#heading=h.ke91xe1nponr

Engineering Ticket Description:

If a field in the command is found to be encrypted with an underlying type string, then return an error. 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Ravind Kumar (Inactive) [ 31/Jul/19 ]

Integrated into ongoing work on automatic field level encryption

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