-
Notifications
You must be signed in to change notification settings - Fork 38
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
Take superseding schema into account during validation #751
Comments
spenes
added a commit
that referenced
this issue
Mar 2, 2023
spenes
added a commit
that referenced
this issue
Mar 17, 2023
This was referenced Mar 28, 2023
Merged
spenes
added a commit
that referenced
this issue
Apr 18, 2023
spenes
added a commit
that referenced
this issue
Apr 19, 2023
spenes
added a commit
that referenced
this issue
Apr 19, 2023
spenes
added a commit
that referenced
this issue
May 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We introduced a new schema metadata field: 'supersededBy'. As the name implies, this field will be used to specify whether schema is superseded by another schema. If it is superseded, superseding schema will be used during validation. Necessary changes are made for this feature on the Iglu Scala Client. On Enrich, we need to bump Iglu Scala Client version. Also, we need to update the part where validation performed in the Enrich.
check
function will return superseding schema version and Enrich should replace superseded schema version in the event with superseding schema version. Also, it will add additional metadata to the event as context to specify the schema version that is replaced.The text was updated successfully, but these errors were encountered: