[SERVER-8315] Immutable Collections Created: 24/Jan/13 Updated: 06/Dec/22 Resolved: 04/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | daniel.roberts@10gen.com | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Provide the ability to specify some collections as immutable. Once a document has been written to a collection it cannot be updated or deleted. An immutable collection should also be tamper-evident. This requirement comes from regulation and compliance drivers where data/audit trails have to be Written Once but Read Many (WORM) times. |
| Comments |
| Comment by Richard Case [ 23/Apr/13 ] |
|
Working in a Bank this would be essential for auditing and compliance purposes. |