cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Uncertainty on Databricks job variables: {{run_id}}, {{parent_run_id}}.

AndrewSilver
New Contributor II

In Azure's Databricks jobs, {{run_id}} and {{parent_run_id}} serve as variables. In jobs with multiple tasks, {{run_id}} aligns with task_run_id, while {{parent_run_id}} matches job_run_id. In single-task jobs, {{parent_run_id}} aligns with task_run_id, yet {{run_id}}'s specific correlation remains unclear—potentially job_run_id.

1 REPLY 1

kulkpd
Contributor

I am using job with single task and multiple retry.
Upon job retry the run_id get changed, I tried to using  {{parent_run_id}} but never worked so switched to 
val parentRunId = dbutils.notebook.getContext.tags("jobRunOriginalAttempt")

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group