You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/reference-yaml-schedule.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Customer can directly use `create_job: azureml:<job_name>` or can use the follow
77
77
| Key | Type | Description | Allowed values |
78
78
| --- | ---- | ----------- | -------------- |
79
79
|`type`| string |**Required.** Specifies the job type. Only pipeline job is supported.|`pipeline`|
80
-
|`job`| string |**Required.** Define how to reference a job, it can be `azureml:<job_name>` or a local pipeline job yaml such as `file:hello-pipeline.yml`.||
80
+
|`job`| string |**Required.** Define how to reference a job, it can be `azureml:<job_name>` or a local pipeline job yaml such as `.\hello-pipeline.yml`.||
81
81
|`experiment_name`| string | Experiment name to organize the job under. Each job's run record will be organized under the corresponding experiment in the studio's "Experiments" tab. If omitted, we'll take schedule name as default value. ||
82
82
|`inputs`| object | Dictionary of inputs to the job. The key is a name for the input within the context of the job and the value is the input value.||
83
83
|`outputs`|object | Dictionary of output configurations of the job. The key is a name for the output within the context of the job and the value is the output configuration.||
0 commit comments