Data Modification when schema updates

[VivekVinushanth]

Currently, we are working on synchronizing identity attribute schema updates from IS into CDS. However, these schema changes also need to be reflected in existing profile data. Updating attributes across every stored profile individually would be operationally expensive and difficult to manage at scale.

What would be a suitable approach to handle this efficiently? One option could be to store profile attribute values generically (for example, as strings) within JSON, and then rely on the schema definition at read, update, or render time to interpret and enforce the correct data type. Would this be a reasonable and scalable design choice?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!