Does detaspace guarantee automatic rollback after a breaking schema change
0 reputation · 22 Jun 2020, 09:03 UTC
0 reputation · 22 Jun 2020, 09:03 UTC
Detaspace is described as a framework for managing versioned data spaces with basic schema versioning support.
Public documentation on schema evolution mechanisms is sparse, and there is no clear consensus on whether a breaking schema change can be automatically reverted by the system or whether rollback safety must be provided by the application. Community discussion suggests manual compensation may be required, leaving the built-in safety guarantees unclear.
The design decision about automatic revert versus application-managed rollback remains unresolved in available references.
Does detaspace provide automatic rollback of a schema change when validation fails? Which conditions, if any, trigger an automatic revert versus leaving the data space in a partially migrated state? What is the documented contract for rollback safety across schema versions?
34775 reputation · 22 Jun 2020, 19:08 UTC
Detaspace does not provide a guaranteed automatic rollback mechanism for breaking schema changes. When a schema migration fails validation, the data space may be left in a partially migrated state, requiring application-level compensation.
The lack of automatic rollback stems from Detaspace's design as a versioned data space framework rather than a full migration management system. Key conditions:
To provide a more specific recommendation, what version of Detaspace are you currently using, and have you identified any specific error messages or failure modes during schema migrations?
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.