[DOCS-12398] Docs for SERVER-38900: Implement JSON Schema parsing for "encrypt" Created: 28/Jan/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.8, 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-38900 Implement JSON Schema parsing for "en... Closed
Duplicate
Participants:
Days since reply: 4 years, 28 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

Please ping me (Nick) if you have any questions about what to document here. I think it makes sense to include the 'encryptMetadata' keyword in the same DOCS ticket.

Engineering Ticket Description:

  • Can be present anywhere in the schema, including top-level.
  • Suggest starting with a new "translateEncryptionKeywords" method at the[ entry point in the parser|https://github.com/mongodb/mongo/blob/83a494cb0a1afca5cfaaf9d29eeb8a2ce1e02264/src/mongo/db/matcher/schema/json_schema_parser.cpp#L1355].
  • Resulting match expression should contain the new $_internalSchemaBinDataSubType expression.
  • This ticket should only implement the parsing required for mongod to understand the new keywords, no mongocryptd/FLE specific logic. For now, require that the "encrypt" argument is an empty object.

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 ]

Duplicates ongoing FLE work

 

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