Clustered Collections listIndexes should show TTL

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor - P4
    • 7.3.0-rc0, 7.0.18
    • Affects Version/s: 6.0.0
    • Component/s: None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v7.0, v6.0
    • Hide 
      db.createCollection( "rule_wf_session_continue_new", { clusteredIndex: {key: {_id: 1},unique: true }, expireAfterSeconds: 15552000 }) 

      db.rule_wf_session_continue_new.getIndexes() 

      [
{
    v: 2,
    key: { _id: 1 },
    name: '_id_',
    unique: true,
    clustered: true
  }
]
      Show
      db.createCollection( "rule_wf_session_continue_new" , { clusteredIndex: {key: {_id: 1},unique: true }, expireAfterSeconds: 15552000 }) db.rule_wf_session_continue_new.getIndexes() [ { v: 2, key: { _id: 1 }, name: '_id_', unique: true, clustered: true } ]
    • Execution Team 2024-01-08, Execution Team 2024-01-22
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Clustered collections allow for the creation of a TTL property to be created on the "clustered index" yet we only show the TTL option as part of listCollections today and not as part of listIndexes. The listIndexes spec omits the TTL properties

      The expected output of listIndexes should include the TTL as part of the index spec.

            Assignee:
            Brad Cater
            Reporter:
            Michael Gargiulo
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: