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
Fix #3217 - Test case props should be unique #3220
Conversation
Schema Change Detected. Needs ingestion-core version bump Please run |
test_case = ColumnTestCase.parse_obj(obj) | ||
|
||
# TODO: we should parse this properly | ||
# assert isinstance(test_case.config, ColumnValuesToBeNotNull) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to be fixed
[open-metadata-ingestion] Kudos, SonarCloud Quality Gate passed! |
[catalog] Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
I'll merge this in to continue with the testing. Let me know if there's anything we'd need to change here |
"value": { | ||
"description": "Expected number of columns to equal to a {value}", | ||
"columnCount": { | ||
"description": "Expected number of columns to equal to a {value}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "Expected number of columns to equal to a {value}", | |
"description": "Expected number of columns to equal to a {columnCount}", |
Describe your changes :
This PR fixes #3217
When parsing JSONs into pydantic classes we need the
config
dict to be unique, otherwise pydantic messes up and does not pick the proper class. In this PR I am updating some names of properties to offer the unicity to the parser, but we will need to maybe rethink a bit the defs.We will still need to fix the
columnValuesToBeUnique
vs.columnValuesToBeNotNull
. As config is empty in these cases, we cannot guarantee that the proper class gets parsed. cc @harshach I'll open a new issue for them.cc @Sachin-chaurasiya @ShaileshParmar11, please review the updated JSONs in case we need to make some naming changes in the UI.
Thanks,
Type of change :
Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.
Checklist:
Reviewers