[DOCS-10819] Downgrade from 3.4 to 3.2 instructions do not work with auth enabled and views created Created: 21/Sep/17  Updated: 29/Oct/23  Resolved: 26/Sep/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Blocker - P1
Reporter: Kevin Arhelger Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 20 weeks, 1 day ago

 Description   

https://docs.mongodb.com/manual/release-notes/3.4-downgrade/

Section 2:

In each database that contains views, drop the system.views collection to drop all views in that database.

Users in deployments with authorization enabled cannot drop system collections.

This breaks the downgrade process for anyone using auth that has ever created a view.



 Comments   
Comment by Githook User [ 26/Sep/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-10819: requirements for dropping system.views collection
Branch: v3.4
https://github.com/mongodb/docs/commit/05c2e5fabe83aa8e7628309576121337ac720840

Comment by Githook User [ 26/Sep/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-10819: requirements for dropping system.views collection
Branch: master
https://github.com/mongodb/docs/commit/1092fad3e5b7e989ab0a832efc7e6ecb0696bf61

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