MetaDataEvolutionValidator now validates synthetic record type evolution#4121
Draft
alecgrieser wants to merge 5 commits into
Draft
MetaDataEvolutionValidator now validates synthetic record type evolution#4121alecgrieser wants to merge 5 commits into
alecgrieser wants to merge 5 commits into
Conversation
alecgrieser
force-pushed
the
04022-mdev-synthetic-types
branch
from
d9f73c9 to
e218f4e
Compare
…ution The `MetaDataEvolutionValidator` has been udpated here to look at the synthetic types in the meta-data. This allows it to validate that the data held in join indexes and unnested indexes is not incorrectly updated during meta-data evolution. There are largely analogous paths followed for the two current synthetic types, `JoinedRecordType`s and `UnnestedRecordType`s. This resolves FoundationDB#4022.
alecgrieser
force-pushed
the
04022-mdev-synthetic-types
branch
from
e218f4e to
04e00b5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
MetaDataEvolutionValidatorhas been udpated here to look at the synthetic types in the meta-data. This allows it to validate that the data held in join indexes and unnested indexes is not incorrectly updated during meta-data evolution. There are largely analogous paths followed for the two current synthetic types,JoinedRecordTypes andUnnestedRecordTypes.This resolves #4022.