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

[docs] remove note that concurrency is only supported for non-sqlite databases #26579

Merged
merged 1 commit into from
Dec 18, 2024
Merged

[docs] remove note that concurrency is only supported for non-sqlite databases #26579

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 0 additions & 5 deletions docs/content/guides/limiting-concurrency-in-data-pipelines.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -391,11 +391,6 @@ height={1638}

### Limiting op/asset concurrency across runs

<Note>
This feature is experimental and is only supported with Postgres/MySQL
storages.
</Note>

#### For specific ops/assets

Limits can be specified on the Dagster instance using the special op tag `dagster/concurrency_key`. If this instance limit would be exceeded by launching an op/asset, then the op/asset will be queued.
Expand Down
Loading