QPQ-AG/mnesia_rocksdb
11
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Migrate table encoding and type #11

Open
uwiger wants to merge 3 commits from uw-migration into master
pull from: uw-migration
merge into: QPQ-AG:master
Conversation 0 Commits 3 Files Changed 4
+1639 -41
uwiger commented 2026-08-11 02:43:57 +09:00
Owner
Copy Link
Copy Source

Maybe it's just me, but I've managed to make the error a few times that I've created a table as a set only to later realize that it should have been an ordered_set.
Mnesia doesn't support changing this, and in mnesia_rocksdb, we have the added complication that the change may involve re-coding each object in the table.

This PR makes it possible to do this.
mnesia_rocksdb_admin:change_table_type/[3,4] allow for changing the table type between sext and ordered_set, and if need be, migrating the serialization of the data.
This can be done either synchronously or asynchronously, and the migration process is stored persistently in the admin metadata table, and can be resumed after restart.

mnesia_rocksdb_admin:migrate_encoding/[3,4] support doing the re-coding manually, but using the above wrapper is strongly recommended.

See the test/mnesia_rocksdb_migration_SUITE for examples of use.

Maybe it's just me, but I've managed to make the error a few times that I've created a table as a `set` only to later realize that it should have been an `ordered_set`. Mnesia doesn't support changing this, and in `mnesia_rocksdb`, we have the added complication that the change may involve re-coding each object in the table. This PR makes it possible to do this. `mnesia_rocksdb_admin:change_table_type/[3,4]` allow for changing the table type between `sext` and `ordered_set`, and if need be, migrating the serialization of the data. This can be done either synchronously or asynchronously, and the migration process is stored persistently in the admin metadata table, and can be resumed after restart. `mnesia_rocksdb_admin:migrate_encoding/[3,4]` support doing the re-coding manually, but using the above wrapper is strongly recommended. See the `test/mnesia_rocksdb_migration_SUITE` for examples of use.
uwiger added 3 commits 2026-08-11 02:43:58 +09:00
WIP migrate table encoding 1a99fec600
WIP implement change_table_type/3 9f00d75654
Improve consistency, add test cases for change_table_type() ca242b72ac
uwiger requested review from dimitar.p.ivanov 2026-08-11 02:43:58 +09:00
uwiger requested review from hans_sv 2026-08-11 02:43:58 +09:00
uwiger requested review from spivee 2026-08-11 02:43:58 +09:00
uwiger requested review from zxq9 2026-08-11 02:43:58 +09:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin uw-migration:uw-migration
git checkout uw-migration
Sign in to join this conversation.
Reviewers
No Reviewers
hans_sv
spivee
zxq9
dimitar.p.ivanov
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 pig lipstick
Muggle-facing enhancements
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Dagadunn Pickmick apex132 dimitar.p.ivanov flambard (Markus Flambard) gchewy hans_sv pharpend spivee (Jarvis Carroll) thescientress (Cecille de Jesus) uwiger (Ulf Wiger) zxq9 (Craig Everett)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QPQ-AG/mnesia_rocksdb#11
Delete Branch "uw-migration"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?