[DOCS-9464] Consider documenting behavior when tampering with system.views Created: 02/Dec/16 Updated: 24/Mar/23 Resolved: 24/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 45 weeks, 5 days ago | ||||||||
| Epic Link: | 3.4: Views | ||||||||
| Description |
|
We should consider documenting the behavior of mongod when users manually tamper with the system.views collection. I'm not sure if this level of detail is appropriate for the manual, given that if users follow the rules and don't touch system.views, none of this should be a problem. Here's the behavior: as of release 3.4.0, users who insert invalid documents into system.views will cause all views-related operations to fail on that server. It also prevents running listCollections. Operations performed through mongos, even when not run on a view, may fail because mongos will try to run listCollections. I'm fine if we don't document this, but we should ensure that there's a note in the views page that says "don't mess with system.views". |
| Comments |
| Comment by Sarah Olson [ 24/Mar/23 ] |
|
Closing this out on the grounds that:
Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree. |