Overview
run_ml_job is Stage 3a of the pipeline (alternative to run_dl_job). It triggers the ml-worker-job pipeline job, which trains a classical machine learning model using scikit-learn on the feature-engineered dataset and generates per-ticker price predictions.
The tool blocks until the job completes and returns the output blob URL.
Parameters
Blob storage URL pointing to a
feature_engine_*.json file.This is the output_url returned by run_feature_worker.Blob storage URL pointing to a
data_extractor_*.json file.This is the output_url returned by run_data_extraction. Required alongside feature_url
for proper train/test date alignment.ML model configuration.
Returns
| Field | Description |
|---|---|
status | Job terminal status (Succeeded) |
output_url | Full HTTPS URL to the output blob — pass to run_po_job |
output_name | Blob filename |
execution_name | Job execution ID for audit/debugging |
Example
Resources
| Resource | Value |
|---|---|
| Container Apps Job | ml-worker-job |
| Container name | ml-worker-job |
| Env vars injected | FEATURE_URL, DATA_EXTRACTOR_URL, CONFIG |
| Output blob prefix | ml_engine_ |
| Timeout | 600 seconds |
Next Step
Passoutput_url to run_po_job as input_url.
If you prefer a neural network approach, use
run_dl_job instead — it produces
an nn_engine_*.json blob that is equally compatible with run_po_job.