From 8233533dcd0ab540dd975097839d7badf8ce3b48 Mon Sep 17 00:00:00 2001 From: Sharmeelee Bijlani Date: Fri, 10 Sep 2021 13:20:03 -0700 Subject: [PATCH] Update aml-pipelines-use-databricks-as-compute-target.ipynb --- .../aml-pipelines-use-databricks-as-compute-target.ipynb | 1 + 1 file changed, 1 insertion(+) diff --git a/how-to-use-azureml/machine-learning-pipelines/intro-to-pipelines/aml-pipelines-use-databricks-as-compute-target.ipynb b/how-to-use-azureml/machine-learning-pipelines/intro-to-pipelines/aml-pipelines-use-databricks-as-compute-target.ipynb index 729da267..48adf903 100644 --- a/how-to-use-azureml/machine-learning-pipelines/intro-to-pipelines/aml-pipelines-use-databricks-as-compute-target.ipynb +++ b/how-to-use-azureml/machine-learning-pipelines/intro-to-pipelines/aml-pipelines-use-databricks-as-compute-target.ipynb @@ -857,6 +857,7 @@ "Users are used to being able to use Run.get_context() to retrieve the parent_run_id for a given run_id. In DatabricksStep, however, a little more work is required to achieve this.\r\n", "\r\n", "The solution is to parse the script arguments and set corresponding environment variables to access the run context from within Databricks.\r\n", + "Note that this workaround is not required for job clusters. \r\n", "\r\n", "Here is a code sample:" ],