Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update backfills docs with more up to date info on single runs #23724

Merged
merged 2 commits into from
Dec 20, 2024
Merged

Update backfills docs with more up to date info on single runs #23724

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9d10a05
Update backfills docs with more up to date info on single runs
Rhiyo Aug 18, 2024
898e1ed
make mdx-format
cmpadden Dec 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/content/concepts/partitions-schedules-sensors/backfills.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,9 @@ By default, if you launch a backfill that covers `N` partitions, Dagster will la
Dagster supports backfills that execute as a single run that covers a range of partitions, such as executing a backfill as a single Snowflake query. After the run completes, Dagster will track that all the partitions have been filled.

<Note>
Single-run backfills only work for backfills that target assets directly, i.e.
those launched from the asset graph or asset page. Backfills launched from the
Job page will not respect the backfill policies of assets included in the job.
Single-run backfills only work if they are launched from the asset graph or
asset page, or if the assets are part of an asset job that shares the same
backfill policy across all included assets.
</Note>

To get this behavior, you need to:
Expand Down
Loading