[SERVER-25723] don't terminate in presence of invalid views Created: 22/Aug/16  Updated: 02/Sep/16  Resolved: 24/Aug/16

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.3.12

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

Issue Links:
Related
is related to SERVER-25680 Commands should check for a collectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:
Steps to reproduce

python buildscripts/resmoke.py --executor=jstestfuzz_replication repro.js

repro.js

var viewsDB = db.getSiblingDB('views_stats');
assert.writeOK(viewsDB.system.views.insert({z: '\0\uFFFFf'}));
 
// Wait for the invalid view definition to be replicated to the secondary and then drop the
// database.
assert.writeOK(db.await_repl.insert({}, {writeConcern: {w: 2}}));
viewsDB.dropDatabase();

Participants:
Linked BF Score: 0

 Description   

As the systems.views collection is directly writable, we should be more forgiving when encountering invalid views.



 Comments   
Comment by Githook User [ 24/Aug/16 ]

Author:

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

Message: SERVER-25723 do not terminate in presence of invalid views
Branch: master
https://github.com/mongodb/mongo/commit/2ce5f3b0afebbb10a70e5239e3790508efde11c9

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