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

Change unstable to true for fields that are not meant to be included in the stable API

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2022-04-04

      We should change recordPreImages, ignoreUnknownIndexOptions, isTimeseriesNamespace, runtimeConstants to unstable: true. See explanations in comments

      We may also need to add them to the IGNORE_UNSTABLE_LIST.

      The changes from https://github.com/mongodb/mongo/commit/e818cd876ed3b492517400a3da3f687fbe13d8aa had added unstable:false to a number of command parameters, but recordPreImages is intentionally undocumented and only used by Realm, so it should be changed back to unstable: true. https://github.com/mongodb/mongo/blob/330c702d55b4a2cfb98dd86630c7e7820e5657c1/src/mongo/db/coll_mod.idl#L155-L160

      Edit: We cannot change isTimeseriesNamespace or runtimeConstants in update and findAndModify to unstable: true at this moment because it needs to be stable to pass parsing validation in shards. See SERVER-65002

            Assignee:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Reporter:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: