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

createIndexes should confirm that index options are valid in respect to the underlying collection

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Hide 

      > db.createCollection("test", {capped:true, size: 102400})
      		 
      { "ok" : 1 }
      		 
      > db.test.ensureIndex({foo:1}, {expireAfterSeconds: 10})
      		 
      {
      		 
              "createdCollectionAutomatically" : false,
      		 
              "numIndexesBefore" : 1,
      		 
              "numIndexesAfter" : 2,
      		 
              "ok" : 1
      		 
      }
      		 
      > db.test.insert({foo:new Date()})
      		 
      WriteResult({ "nInserted" : 1 })


      2016-01-19T18:17:11.210+1100 I STORAGE  [TTLMonitor] failing remove on a capped ns test.test
      		 
      2016-01-19T18:17:11.210+1100 E INDEX    [TTLMonitor] Error processing ttl index: { v: 1, key: { foo: 1.0 }, name: "foo_1", ns: "test.test", expireAfterSeconds: 10.0 } -- 10089 cannot remove from a capped collection

      Show
      > db.createCollection("test", {capped:true, size: 102400}) { "ok" : 1 } > db.test.ensureIndex({foo:1}, {expireAfterSeconds: 10}) { "createdCollectionAutomatically" : false, "numIndexesBefore" : 1, "numIndexesAfter" : 2, "ok" : 1 } > db.test.insert({foo:new Date()}) WriteResult({ "nInserted" : 1 }) 2016-01-19T18:17:11.210+1100 I STORAGE [TTLMonitor] failing remove on a capped ns test.test 2016-01-19T18:17:11.210+1100 E INDEX [TTLMonitor] Error processing ttl index: { v: 1, key: { foo: 1.0 }, name: "foo_1", ns: "test.test", expireAfterSeconds: 10.0 } -- 10089 cannot remove from a capped collection
    • Execution Team 2021-11-01, Execution Team 2021-11-15, Execution Team 2021-11-29

    Description

      As reported in SERVER-769, it is possible to create a TTL index on a capped collection. This results in failed TTL document deletion once expiration is hit.

      We should audit which index options are invalid for specific collection options and add validation so that createIndexes will fail if specified.

      Attachments

        Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-61545 Remove feature compatibility version casing around TTL indexes on capped collections

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-43820 createIndex does not validate index option values

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-769 Validate top-level & index spec field names for the createIndexes command

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-53739 Validate all createIndexes options

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-52539 Specify input/output to createIndexes command in IDL

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-53765 Validate index entries at catalog layer

          • Major - P3 - Major loss of function.
          • Backlog

          Activity

            People

              gabriel.marks@mongodb.com Gabriel Marks
              james.wahlin@mongodb.com James Wahlin
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: