Support asset-backed defaults on uri_file/uri_folder/mltable component inputs - #48676
Draft
lavakumarrepala with Copilot wants to merge 3 commits into
Draft
Support asset-backed defaults on uri_file/uri_folder/mltable component inputs#48676lavakumarrepala with Copilot wants to merge 3 commits into
lavakumarrepala with Copilot wants to merge 3 commits into
Conversation
|
Azure Pipelines: 10 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
…nt inputs Co-authored-by: lavakumarrepala <221403938+lavakumarrepala@users.noreply.github.com>
…oup behavior Co-authored-by: lavakumarrepala <221403938+lavakumarrepala@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Implement support for asset-backed defaults on non-primitive inputs
Support asset-backed defaults on uri_file/uri_folder/mltable component inputs
Aug 21, 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.
The component schema accepts a
defaulton asset ports (InputPortSchema.default = fields.Str()), butload_component()rejected it withDefault value of Input cannot be set: Non-primitive type Input has no default value., becauseInput._update_default()rejected every non-Nonedefault on a non-primitive type.Changes
constants/_component.py— addedIOConstants.ASSET_TYPES_SUPPORTING_DEFAULT(uri_folder,uri_file,mltable) and added"default"to those entries inINPUT_TYPE_COMBINATIONso parameter-combination validation permits it.mlflow_model/custom_modelare intentionally left out.entities/_inputs_outputs/input.py— new_supports_asset_defaultproperty;_update_default()now stores a string asset/path reference as-is for the supported types. Non-string defaults (123,True, a nestedInput) raiseUserErrorExceptionwith a message keeping the establishedDefault value of Input '<name>' cannot be setprefix, which the dslgrouptests assert on. Unsupported non-primitive types keep the original error. Docstring and the generic__init__overload updated.defaultis already inInput._IO_KEYS, so_to_dict,_to_rest_object,_from_rest_objectandInputPortSchemapreserve the reference, type, mode and optional semantics through YAML and REST round trips.BaseNode._validate_inputs/PipelineJobalready skips inputs wheremeta.default is not None, so an omitted input is no longer an error and the service applies the default; an explicit value still overrides it without mutating the component definition.tests/component/unittests/test_input_defaults.pyplusinput_asset_defaults_component.yml,input_asset_defaults_pipeline_component.yml, andinvalid/input_asset_defaults_invalid_component.yml, covering direct construction, YAML dump/reload, REST round trip, the customer repro for command and pipeline components, override/no-mutation, invalid defaults, and primitive-default regressions.Notes / follow-up
Inputobject asdefaultis not introduced, since the wire contract carries a string.azuremlschemas.azureedge.netschemas live outside this repo and should be aligned separately.