Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-1331

sh.status() should omit deprecated fields from config.version

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 2.0.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • 3
    • Needed
    • Hide

      Now sh.status won't show all information of the sharding status, as we removed some deprecated fields. Probably a note stating that only relevant fields are shown should be enough.

      Removed fields from output:

      minCompatibleVersion
      currentVersion
      excluding
      upgradeId
      upgradeState

      Show
      Now sh.status won't show all information of the sharding status, as we removed some deprecated fields. Probably a note stating that only relevant fields are shown should be enough. Removed fields from output: minCompatibleVersion currentVersion excluding upgradeId upgradeState

      sh.status() includes a dump of the config.version document.
      This document could contain the following fields:

      • minCompatibleVersion
      • currentVersion
      • excluding
      • clusterId
      • upgradeId
      • upgradeState

      All of them except clusterId are deprecated and are not used in any of the currently supported mongodb version (4.2 -> 6.0), in fact the usage of these fields have been replaced by the more robust feature compatibility version mechanism. We started removing those fields in SERVER-68888.

      Including those fields in the sh.status command can be misleading for our customer, this is especially true for minCompatibleVersion and currentVersion fields that are always equal to 5 and 6 and can be confused with the real value of the FCV version.

      My proposal is to include in sh.status() only the clusterId field that is the only meaningful one in config.version.

            Assignee:
            kevin.mas@mongodb.com Kevin Mas Ruiz
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.