Title: Add option to include upstream tasks for `bundle run --only` · Issue #4244 · databricks/cli · GitHub
Open Graph Title: Add option to include upstream tasks for `bundle run --only` · Issue #4244 · databricks/cli
X Title: Add option to include upstream tasks for `bundle run --only` · Issue #4244 · databricks/cli
Description: Describe the issue When developing a Databricks Job, it is good practice to only execute the tasks that got updated. Oftentimes upstream or downstream tasks have to be executed as well to reproduce the pipeline reliably. Currently, Datab...
Open Graph Description: Describe the issue When developing a Databricks Job, it is good practice to only execute the tasks that got updated. Oftentimes upstream or downstream tasks have to be executed as well to reproduce...
X Description: Describe the issue When developing a Databricks Job, it is good practice to only execute the tasks that got updated. Oftentimes upstream or downstream tasks have to be executed as well to reproduce...
Opengraph URL: https://github.com/databricks/cli/issues/4244
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add option to include upstream tasks for `bundle run --only`","articleBody":"# Describe the issue\nWhen developing a Databricks Job, it is good practice to only execute the tasks that got updated. Oftentimes upstream or downstream tasks have to be executed as well to reproduce the pipeline reliably.\n\nCurrently, Databricks CLI supports executing specific tasks in a Job by means of the `--only` flag but for some reason there is no native way to automatically include upstream or downstream tasks of the selected tasks. However, via the UI, it is possible to do this:\n\n\u003cimg width=\"1025\" height=\"668\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/198a6ff9-1798-4a52-acb6-69d104857926\" /\u003e\n\nIt'd be really great to have a flag `--include-downstream/--include-upstream` to do just that. Ideally, it would be possible to include upstream/downstream tasks on a per-task basis such as [dbt does with its `+` operator](https://docs.getdbt.com/reference/node-selection/graph-operators) (`dbt run --select +model_name+`), but adding a general flag that would do this for all of the tasks selected using the `--only` flag would be a great addition as it is.\n\n## Some examples with expected behaviors:\n#### `databricks bundle run job_name --only task1,task8 --include-upstream`\nWould run task1 *and* its upstream tasks plus task8 *and* its upstream tasks\n\n#### `databricks bundle run job_name --only task1,task8 --include-downstream`\nWould run task1 *and* its downstream tasks plus task8 *and* its downstream tasks\n\n#### `databricks bundle run job_name --only task1,task8 --include-upstream --include-downstream`\nWould run task1 *and* its upstream tasks *and* its downstream tasks plus task8 *and* its upstream tasks *and* its downstream tasks\n\nOtherwise, mimicking dbt `+` operator would also work but I guess it would require far more effort to make happen.\n\n# OS and CLI version\nDatabricks CLI v0.282.0\n\n# Is this a regression?\nNo\n\n# Debug Logs\nN/A","author":{"url":"https://github.com/guizsantos","@type":"Person","name":"guizsantos"},"datePublished":"2026-01-09T17:52:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/4244/cli/issues/4244"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:31432a97-2884-4e30-7e0b-4c3d81e8eab0 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | AE7A:89F46:1F93CC6:29A9FDF:6992D077 |
| html-safe-nonce | 29b1b2ead6879a5052bcbf253853ae7a131b1b7b24558e68f2d4620059675ab2 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBRTdBOjg5RjQ2OjFGOTNDQzY6MjlBOUZERjo2OTkyRDA3NyIsInZpc2l0b3JfaWQiOiI1OTE5MTkyODE2NjUxNzg0MzExIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 07c42a0d032ea03ab8a320ca9a76e3bdba180f16f4d68533b4adc3a6e5cc8ee0 |
| hovercard-subject-tag | issue:3797830676 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/databricks/cli/4244/issue_layout |
| twitter:image | https://avatars.githubusercontent.com/u/4998052?s=400&v=4 |
| twitter:card | summary |
| og:image | https://avatars.githubusercontent.com/u/4998052?s=400&v=4 |
| og:image:alt | Describe the issue When developing a Databricks Job, it is good practice to only execute the tasks that got updated. Oftentimes upstream or downstream tasks have to be executed as well to reproduce... |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | guizsantos |
| hostname | github.com |
| expected-hostname | github.com |
| None | 42c603b9d642c4a9065a51770f75e5e27132fef0e858607f5c9cb7e422831a7b |
| turbo-cache-control | no-preview |
| go-import | github.com/databricks/cli git https://github.com/databricks/cli.git |
| octolytics-dimension-user_id | 4998052 |
| octolytics-dimension-user_login | databricks |
| octolytics-dimension-repository_id | 491883713 |
| octolytics-dimension-repository_nwo | databricks/cli |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 491883713 |
| octolytics-dimension-repository_network_root_nwo | databricks/cli |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 84dcb133269e3cfe6e0296cc85fbacb92cae92bb |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width