Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-25723

don't terminate in presence of invalid views

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.12
    • Component/s: None
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      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();
    • Linked BF Score:
      0

      Description

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

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: