Fix mltable load of registered data asset: restore DataVersionEntity.additional_properties - #48275
Merged
saanikaguptamicrosoft merged 1 commit intoJul 28, 2026
Conversation
…additional_properties The dataset_dataplane TypeSpec (hybrid) migration (Azure#45389) dropped the msrest additional_properties attribute from DataVersionEntity. The mltable package's local data-asset resolution path (MLClient.jobs._dataset_dataplane_operations._operation.get) reads additional_properties['isV2'|'legacyDataflow'], so loading a registered MLTable data asset via mltable.load('azureml://.../data/<name>/versions/<v>') raised AttributeError. Restored the attribute as a regeneration-safe compat shim in models/_patch.py returning the un-modeled wire keys. Wire contract unchanged.
saanikaguptamicrosoft
requested review from
JustinFirsching,
NonStatic2014,
achauhan-scc,
arunsu,
jayesh-tanna,
kingernupur,
nick863,
novaturient95,
rtanase,
sharma-riti and
vivram
as code owners
July 27, 2026 09:29
|
Azure Pipelines: Successfully started running 1 pipeline(s). 9 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Restores MLTable loading compatibility after the dataset dataplane TypeSpec migration.
Changes:
- Adds an
additional_propertiescompatibility shim. - Adds regression tests for modeled and unmodeled fields.
- Documents the fix in the changelog.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
models/_patch.py |
Restores access to unmodeled wire properties. |
test_dataset_dataplane_additional_properties.py |
Tests compatibility behavior and edge cases. |
CHANGELOG.md |
Records the MLTable loading fix. |
kingernupur
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Notes
The dataset_dataplane TypeSpec (hybrid) migration (Azure AI ML to TSP #45389) dropped the msrest additional_properties attribute from DataVersionEntity. The mltable package's local data-asset resolution path (MLClient.jobs._dataset_dataplane_operations._operation.get) reads additional_properties['isV2'|'legacyDataflow'], so loading a registered MLTable data asset via mltable.load('azureml://.../data//versions/') raised AttributeError. Restored the attribute as a regeneration-safe compat shim in models/_patch.py returning the un-modeled wire keys. Wire contract unchanged.
Testing
The failing two mltable notebook samples are succeeding now
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines