don't terminate in presence of invalid views

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.12
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • Hide
      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();
      Show
      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();
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

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

              Assignee:
              Geert Bosch
              Reporter:
              Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: