Get intermittent errors when materializing multiple dlt assets to duckdb with concurrency 1 #26848
Labels
integration: duckdb
Related to DuckDB integrations
integration: embedded-elt
Related to dagster-embedded-elt which uses Sling and data Load Tool (dlt)
type: bug
Something isn't working
What's the issue?
If materialize multiple assets using the dlt integration to a destination of duckdb I sometimes get an error trying to open the duckdb file
e.g.
What did you expect to happen?
I expect only a single asset to be materialized at the same time and not to get the error from duckdb if only one asset is using it
How to reproduce?
this repo has some examples of dlt to duckdb
https://github.com/[pwr-philarmstrong/dlt_with_dagster_example2](https://github.com/pwr-philarmstrong/dlt_with_dagster_example2/tree/master)/tree/master
if you try and materialize the assets groups that don't have file in the name then you get the error for one or more of the assets
in this example there is only one asset that uses dlt_assets_incremental__family_pipeline.duckdb so the issue is unlikely to be related to concurrency
Dagster version
dagster, version 1.9.6
Deployment type
Local
Deployment details
using source of mysql+pymysql://[email protected]:4497/Rfam
and destination of local filesystem or duckdb. each asset script has output_dir var for the local filesystem
Additional information
You might get other errors such from dlt like access denied and timeouts but they are not related to the duckdb access issue
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: