As per the database, each schema modification begs the question of data migration... (recently the change from occurrence to snapshot, the snapshot naming convention change, the release question, etc...).
We will double this issue for the journal...
Possible solutions:
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T424 swh-journal: persistent journal infrastructure to record additions to the swh-storage | ||
| Migrated | gitlab-migration | T1279 swh-journal: The schema migration problem |
Since this "migration problem" also concerns cassandra, maybe an simple approach would be to add a Final version attribute to all model entities (a simple monotonic integer).
I like the Final version attribute idea. But to be clear, this means we will need to add successive versions as extra classes in swh.model.model when we change the schema (which is not necessarily a bad thing), and remove them when we are sure they are not around anymore