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

Remove logic to fix invalid expireAfterSeconds values post-creation

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Storage Execution

    Description

      We introduced additional validation code for TTL indexes in an earlier release cycle, as well as code to fix invalid expireAfterSeconds values for existing indexes. Additionally, we introduced similar logic to normalize any non-integer expireAfterSeconds values to integer values in SERVER-77828.

      After we have gone through a major release cycle, we will know that future versions of the server will never see those invalid index specs on disk, as they would have to have first upgraded through a patched version which would fix the spec.

      While we'll always need the validation code during index creation/modification, we can remove some of the extra logic associated with fixing existing indexes.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: