-
Notifications
You must be signed in to change notification settings - Fork 3k
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): lineage for SageMaker model endpoints and groups #2894
feat(ingest): lineage for SageMaker model endpoints and groups #2894
Conversation
"Deleting": EndpointStatusClass.DELETING, | ||
"Failed": EndpointStatusClass.FAILED, | ||
"Unknown": EndpointStatusClass.UNKNOWN, | ||
} |
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.
do we need this level of granularity in our model as well?
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.
I think so – it may be a little too detailed for our current pull-based integration, but it will be useful once we have push-based functionality.
@@ -55,6 +55,7 @@ def check_golden_file( | |||
# if updating a golden file that doesn't exist yet, load the output again | |||
if update_golden and not golden_exists: | |||
golden = load_json_file(output_path) | |||
shutil.copyfile(str(output_path), str(golden_path)) |
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.
If the golden doesn't exist, doesn't it make sense to just set it to None or []
-> there is a diff -> we update the underlying file
This logic seems a bit too complex, but we can address this in a follow up
Ownership, | ||
Status, | ||
Deprecation, | ||
BrowsePaths |
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.
will ml model endpoints be browsable? probably not, right? I imagine these will just be linked via ml models
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.
No they won't – will remove
/** | ||
* Name of the MLModelEndpoint | ||
*/ | ||
@Searchable = { | ||
"fieldType": "TEXT_PARTIAL", | ||
"enableAutocomplete": true, | ||
"boostScore": 10.0 | ||
} | ||
name: string |
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.
where do these names come from?
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.
SageMaker – you can set a name for an endpoint
metadata-models/src/main/pegasus/com/linkedin/ml/metadata/MLModelEndpointProperties.pdl
Outdated
Show resolved
Hide resolved
metadata-models/src/main/pegasus/com/linkedin/ml/metadata/MLModelEndpointProperties.pdl
Outdated
Show resolved
Hide resolved
metadata-models/src/main/pegasus/com/linkedin/ml/metadata/MLModelGroupProperties.pdl
Outdated
Show resolved
Hide resolved
metadata-models/src/main/pegasus/com/linkedin/ml/metadata/MLModelGroupProperties.pdl
Outdated
Show resolved
Hide resolved
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.
LGTM!
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.
LGTM!
Uses the SageMaker lineage graph to extract and infer lineage between models and endpoints as well as models and model groups.
Checklist