[SERVER-52513] FeatureCompatibility should be an independent ServiceContext decoration Created: 30/Oct/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Replication
Participants:

 Description   

We define FeatureCompatiblity here. However, there are some immediate downsides:

  • Checks that reference the version need to write out ServerGlobalParams::FeatureCompatibility instead of simply FeatureCompatiblity.
  • mutableFeatureCompatibility is directly exposed.
  • Our default value does not match our reset value, implying that the state can be accessible but unset. This would be more intuitive if we could provide optionality via either a pointer or an optional.

Generated at Thu Feb 08 05:28:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.