Skip to content

Azure Storage Migrations #533

@sdiachen

Description

@sdiachen

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions