Confirm change that removed maxFeatureCompatibilityVersion

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2026-03-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-102942 removed maxFeatureCompatibilityVersion that was previously in the expression context. We used to set maxFeatureCompatibilityVersion when validateFeaturesAsPrimary was false to try and avoid FCV checks during replication recovery. During replication recovery, we do not need maxFeatureCompatibilityVersion when we are applying oplog entries because we correctly do not check FCV when parsing new query features for views and validators. However we want to confirm in this ticket that there weren't other situations where we relied on maxFeatureCompatibilityVersion.

      See TODOs in code. collection_validator_feature_compatibility_version and view_definition_feature_compatibility_version reference validateFeaturesAsPrimary

            Assignee:
            Justin Seyster
            Reporter:
            Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: