-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Labels
Description
Design migration framework to migrate Azure Storage data
- the system should keep operational when:
- Partition and Row key changed
- new attribute added
- attribute removed (probably through several migrations)
- system should work with previous and current data simultaneously
Implementation thoughts:
- Use some kind of semver to version schema (e.g. index change major version, attribute change minor version)
- Use some kind of transformer in access logic to handle old versions still present in data