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,
...
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 3 months, 3 weeks agoarekm
Most Recent 1 month agoAlejandroU
1 month, 1 week agoThameur01
2 months, 1 week agoThameur01
2 months, 1 week agocf56faf
2 months, 3 weeks agobenni_ale
3 months, 1 week agoKreshu
3 months, 3 weeks agothelio_team
4 months, 1 week agoMDWPartners
8 months, 1 week ago