-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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(ingest/mlflow): add dataset lineage #12837
base: master
Are you sure you want to change the base?
feat(ingest/mlflow): add dataset lineage #12837
Conversation
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
source_type = dataset_input.dataset.source_type | ||
dataset_tags = {k[1]: v[1] for k, v in dataset_input.tags} | ||
dataset = dataset_input.dataset | ||
platform = self._get_dataset_platform_from_source_type(source_type) |
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 this method is being called twice
dataset_reference_urns.append(str(local_dataset_reference.urn)) | ||
# Otherwise, we create a hosted dataset reference and a hosted dataset | ||
else: | ||
hosted_dataset = Dataset( |
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.
imo we should not be generating dataset entities for non mlflow platforms
here we should just do hosted_dataset_urn = DatasetUrn...
. if that urn exists, lineage will show up by default. if it doesn't exist, they'll need to go into the UI and click "show hidden edges" to make them show up
Checklist