[SERVER-26243] Dropping system.views should be allowed Created: 22/Sep/16  Updated: 19/Nov/16  Resolved: 09/Nov/16

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.4.0-rc3

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: read-only-views
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

db.coll.createView("a", "b", []);

Sprint: Integration 2016-10-10, Integration 2016-10-31, Storage 2016-11-21
Participants:

 Description   

There is a left-over check that prohibits dropping system.views while in 3.4 compatibility mode, as at one point the presence of a system.views collection was used to make sure initial sync on 3.2 would fail in 3.4 compatibility mode. However, now we use V2 indexes for that, so this is no longer needed.

Additionally, the design of views requires them to be droppable, as replication may need to drop a system.views collection during rollback. We should also add a test for this.



 Comments   
Comment by Githook User [ 09/Nov/16 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-26243 Allow deletion of system.views and fix/test rollback

This fixes an issue where rollback would loop indefinitely when a collection turns into a view
during rollback and recovery. Also tests dropping views and system.views.
Branch: master
https://github.com/mongodb/mongo/commit/2422b66ef85a139ee5adf55c63e94998954d1a05

Generated at Thu Feb 08 04:11:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.