Uncertainty on Databricks job variables: {{run_id}}, {{parent_run_id}}.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2023 05:06 AM
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2023 09:40 AM
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")
