In addition to supporting migrations of table schema (T75808), it should also be possible to migrate the storage backend-specific implementation of schemas. This will require that a _backend-version attribute be assigned (by the backend itself), so that version mismatches can trigger whatever changes are necessary.
As a use-case, the current ad-hoc dropping of the native secondary index on _domain should be converted to use this mechanism.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Hardikj | T75808 Schema compatibility checking / schema evolution / migration on table creation for table that already exists | |||
| Resolved | Eevans | T97845 backend versioning for restbase-mod-table-cassandra |
This is tentatively complete in https://github.com/eevans/restbase-mod-table-cassandra/tree/backend-vers, but it depends upon https://github.com/wikimedia/restbase-mod-table-cassandra/pull/98, so I'll wait to open a pull request until that has been merged.