Don't FCV-gate new $rank implementation in the context of $rankFusion

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We should only (and always) FCV-gate the new $rank implementation and outputSortKeyMetadata enablement if we are NOT in the context of $rankFusion. This is to allow safe upgrades for both $rankFusion and $setWindowFields queries when the bypassRankFusionFCVGate flag is enabled.

      When doing this, we should add a $setWindowFields query that meets the criteria described in SERVER-111784 to the existing rank_fusion_upgrade_downgrade.js test.

            Assignee:
            Alyssa Clark
            Reporter:
            Alyssa Clark
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: