Test that featureFlagMqlJsEngineGap is handled correctly in upgrade/downgrade scenarios

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Test the new features gated by the feature flag in the following sharded scenarios, with the feature flag enabled:

      • whole cluster on older FCV
      • whole cluster on latest FCV
      • mongos sees latest FCV, at least one shard sees an older FCV
      • mongos sees an older FCV, at least one shard sees the latest FCV

      According to the scope document, new features should be treated as enabled if and only if they are enabled on mongos.

            Assignee:
            Unassigned
            Reporter:
            Henri Nikku
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: