The correct answer is E. https://docs.databricks.com/api/workspace/jobs/getrun
You can visit the link and observe the response sample of the API
{
"job_id": 11223344,
"run_id": 455644833,
job_id is the unique id of the job. run_id is the unique id of the run
Then each task will have its unique run id:
"tasks": [
{
...
"run_id": 2112892,
...
Each job execution (run) gets a unique run_id
This run_id identifies a specific instance of a job run.
It allows tracking of job execution details, logs, and results.
Each task within that job run has a unique task_id
Multi-task jobs have multiple tasks, each assigned a distinct task_id.
The task_id helps in monitoring and retrieving individual task details.
E - but between D & E is a play on the words. Still E seems a tiny bit more explicit. The bottom line the run_id attribute of each task within the job will be different.
Answer E. Job Run (run_id): Each execution of a job has a unique run_id for the entire job.
Task Run (run_id): For jobs with multiple tasks, each task also gets its own run_id, which is distinct from the job's run_id. This run_id for tasks can be used to retrieve individual task outputs.
https://docs.databricks.com/api/workspace/jobs/getrun
"tasks: The list of tasks performed by the run. Each task has its own run_id which you can use to call JobsGetOutput to retrieve the run results. "
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
cales
Highly Voted 5 months, 3 weeks agomohadjhamad
Most Recent 3 weeks, 4 days agoarekm
3 months agoAlejandroU
3 months, 1 week agoThameur01
4 months agoThameur01
4 months agocf56faf
4 months, 3 weeks agobenni_ale
5 months agoKreshu
5 months, 2 weeks agothelio_team
6 months, 1 week agoMDWPartners
10 months, 1 week ago