Set valid default for classificationOrigin #7631
Merged
Conversation
This file contains 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
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.
Description
There is an issue in the XTDB repository reporting errors when saving the classification origin because it is
null. This is the default value set up innew Classification().Most repository level function (archivers, JanusGraph repository, test cases ...) do not set this value. Therefore XTDB, which is technically correct, will encounter a null value from many sources.
This PR changes the default value of
classificationOrigintoClassificationOrigin.ASSIGNEDRelated Issue(s)
odpi/egeria-connector-xtdb#475
Testing
FVTs When this is in main, we will retest XTDB to ensure this issue goes away.
Release Notes & Documentation
No
Additional notes