[DOCS-16390] Investigate changes in SERVER-79496: Ban encryption options being provided in createCollection Created: 19/Sep/23  Updated: 18/Dec/23  Resolved: 13/Nov/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 7.2.0-rc0, Server_Docs_20231120

Type: Task Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Sarah Simpers
Resolution: Done Votes: 0
Labels: request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-79496 Ban encryption options being provided... Closed
Participants:
Days since reply: 20 weeks, 1 day ago

 Description   
Original Downstream Change Summary

createCollection will fail with an IllegalOperation error if the user attempts to pass in WiredTiger encryption options. For example {{db.createCollection("test", {storageEngine: {wiredTiger:

{configString: "encryption=(keyid=key)"}

} })}} will fail.

The encryption option is currently only returned in collStats as part of the WT creationString field. If using that field for creating a collection, the encryption option must be removed.

Description of Linked Ticket

In SERVER-72227 we came to the conclusion that in some cases there can be situations where a collection is mistakenly created with encryption options in the config string. This can happen if an external tool makes a backup and saves the creation string as read from collStats.

These options are ephemeral in nature and should never be inserted into the durable catalog. We should consider banning them from the set of valid user options.


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