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

Ban uses of unstable command parameters with apiStrict: true

XMLWordPrintableJSON

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • Query 2020-11-30, Query 2020-12-14

      In the "API Version Testing" project we added a boolean field "unstable" to mark command parameters in the IDL for API Version 1 commands. Unstable parameters are not guaranteed to be backward-compatible, even though they are parameters of V1 commands. We plan to use the "unstable" field only when comparing old and new releases' IDL definitions of V1 commands; we'll ignore incompatible changes to unstable fields.

      However, arun.banala makes a good suggestion: at runtime, ban the use of unstable parameters in client requests that include apiStrict: true.

            Assignee:
            arun.banala@mongodb.com Arun Banala
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: