-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
feat(cli/datacontract): Add data quality assertion support #8968
feat(cli/datacontract): Add data quality assertion support #8968
Conversation
Co-authored-by: Harshal Sheth <[email protected]>
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.
broadly looks reasonable
@@ -54,7 +54,7 @@ class DataContract(ConfigModel): | |||
freshness: Optional[FreshnessAssertion] = pydantic.Field(default=None) | |||
|
|||
# TODO: Add a validator to ensure that ids are unique | |||
data_quality: Optional[List[DataQualityAssertion]] = None | |||
data_quality: Optional[List[DataQualityAssertion]] = pydantic.Field(default=None) |
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.
interesting - these two are equivalent right?
UpstreamClass, | ||
UpstreamLineageClass, | ||
) | ||
from datahub.specific.dataset import DatasetPatchBuilder |
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.
looks like the base commit isn't set correct?
@asikowitz btw we should probably write some tests for the contracts cli |
What exactly is this contracts CLI going to be used for? Can we provide some examples? Also, we are moving quickly on new assertion types, how should we think about adding new types of assertions into contracts? |
@@ -4,6 +4,8 @@ | |||
from typing_extensions import Literal | |||
|
|||
import datahub.emitter.mce_builder as builder | |||
from datahub.api.entities.datacontract.assertion import BaseAssertion |
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.
Should we also support Volume Assertions + Freshness Assertions?
Or are these already supported
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.
Freshness is supported I believe, or at least a subset of it. Volume not yet
Checklist