Skip to content

Conversation

@Shaddoll
Copy link
Member

Summary

Deprecate unused fields

Type of Change

  • Add new API(s)
  • Add new data type(s)
  • Add new field(s) to existing data type
  • Remove field(s) from data type
  • Remove data type(s)
  • Remove API(s)
  • Other (please provide detailed description)

Data Effect

  • Does it change the data stored in database?

Detailed Description

Mark unused fields deprecated

Impact Analysis

  • Backward Compatibility: Yes
  • Forward Compatibility: Yes

Testing Plan

  • Unit Tests: Not needed
  • Persistence Tests: Not needed
  • Integration Tests: Not needed
  • Compatibility Tests: Not needed

Rollout Plan

  • What is the rollout plan? As normal rollout
  • Does the order of deployment matter? No.
  • Is it safe to rollback? Does the order of rollback matter? Yes. Does not matter.
  • Is there a kill switch to mitigate the impact immediately? No.

@Shaddoll Shaddoll changed the title Deprecate unused active-active fields chore: Deprecate unused active-active fields Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants