Skip to content

Commit ae4ec58

Browse files
Merge pull request #229387 from xiaoharper/patch-2
add is_deterministic in component yaml
2 parents 0b65b5c + e465b7b commit ae4ec58

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/machine-learning/reference-yaml-component-command.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
3434
| `display_name` | string | Display name of the component in the studio UI. Can be non-unique within the workspace. | | |
3535
| `description` | string | Description of the component. | | |
3636
| `tags` | object | Dictionary of tags for the component. | | |
37+
| `is_deterministic` | boolean |This option determines if the component will produce the same output for the same input data. You should usually set this to `false` for components that load data from external sources, such as importing data from a URL. This is because the data at the URL might change over time. | | `true` |
3738
| `command` | string | **Required.** The command to execute. | | |
3839
| `code` | string | Local path to the source code directory to be uploaded and used for the component. | | |
3940
| `environment` | string or object | **Required.** The environment to use for the component. This value can be either a reference to an existing versioned environment in the workspace or an inline environment specification. <br><br> To reference an existing environment, use the `azureml:<environment-name>:<environment-version>` syntax. <br><br> To define an environment inline, follow the [Environment schema](reference-yaml-environment.md#yaml-syntax). Exclude the `name` and `version` properties as they are not supported for inline environments. | | |

0 commit comments

Comments
 (0)