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

FeatureCompatibility should be an independent ServiceContext decoration

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • None
    • Replication

    Description

      We define FeatureCompatiblity here. However, there are some immediate downsides:

      • Checks that reference the version need to write out ServerGlobalParams::FeatureCompatibility instead of simply FeatureCompatiblity.
      • mutableFeatureCompatibility is directly exposed.
      • Our default value does not match our reset value, implying that the state can be accessible but unset. This would be more intuitive if we could provide optionality via either a pointer or an optional.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: