Model Versioning #530
Unanswered
Euan-McVie
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Is there a good practise for using the library with multi-versioned models.
For most changes we will be following additive only when making property changes, but occasionally we may need to make breaking changes that are not backwards compatible and we would prefer to avoid data migration.
We haven't had to do it yet, but are requiring to document the proposed approach so we know how we can attempt it if/when we do.
In the c# code for the rest of our (non-gremlin) Cosmos usage we are using a namespace with suffix
.V1
,.V2
etc. and we then have it included as part of a discriminator.Would following a similar approach work with the built in label discriminator if the c# models have the same name only differing on namespace?
If not then what would be the suggested approach? Adding a
Version
discriminator to our base model? Other?Many Thanks
Euan
Beta Was this translation helpful? Give feedback.
All reactions