Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration to support use of information elsewhere in the persisted cache data #324

Open
bienur opened this issue Mar 21, 2018 · 0 comments

Comments

@bienur
Copy link
Contributor

bienur commented Mar 21, 2018

Currently, Hermes migrates persisted data on a per-entity basis as part of the restore(). Which makes it difficult to migrate based on information stored elsewhere in the persisted cache snapshot.

Consider the following case where the new version of code introduces a new field on User, experimentTreatments2 (an object), to replace/deprecate the old experimentTreatments (an entity array). Rather than dumbly initializes experimentTreatments2 to {}, we want the migration to initialize it with information from experimentTreatments. One can imagine similar situations with need like this. However, it's not something that can be done easily today.

Might be worth considering adding the support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant