-
Notifications
You must be signed in to change notification settings - Fork 13
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
Loading dataset from a different instance that does not have all schemas of the current instance errors #2117
Comments
Do you mean if |
Correct |
@falexwolf I think this is related to the inter-instance tracking, why is the artifact being saved in this case? |
You can only load an artifact if it's saved; otherwise, there is no way to track lineage. The bug here is independent of data lineage but related to not being able to save the artifact. I thought we're meanwhile able to transfer artifacts across instances with mismatching schemas? I'm surprised this doesn't work. I know this is hard to test but we should add a test for a target instance whose schema modules is neither a strict super nor a strict subset of the source instance. |
Looking at the below line in the traceback I believe we in fact don't have a general problem, just a coverage problem for edge cases: 208 if not labels.exists(): Likely, this case isn't covered in the tests and this leads to the bug. |
But saving an artifact works without |
Should be fixed here and added tests: #2132 |
Report
results in
The
get
works but theload()
errors. Only whentrack()
is on.Version information
No response
The text was updated successfully, but these errors were encountered: