Replies: 1 comment
-
You can set concurrency limits for assets using tags https://docs.dagster.io/guides/limiting-concurrency-in-data-pipelines#limiting-opasset-concurrency-across-runs on your asset: @asset(op_tags={"dagster/concurrency_key": "sql"})
def myasset():
df = pd.read_sql("SELECT * FROM .. ") And then run the CLI command dagster instance concurrency set sql 10 And then dagster will never have more than 10 assets with the tag |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'd like to be able to limit the number of materializations per asset directly from the asset definition. Indeed, I execute SQL queries, and depending on the database, I want to avoid making too many queries at the same time.
For example, inspired by snakemake :
This setting will prevent more than 10 instances running at the same time.
Beta Was this translation helpful? Give feedback.
All reactions