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] add note of defer_table_reflect to dlt docs #26628

Merged
merged 1 commit into from
Dec 20, 2024
Merged

[docs] add note of defer_table_reflect to dlt docs #26628

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
10 changes: 10 additions & 0 deletions docs/content/integrations/embedded-elt/dlt.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,16 @@ The <PyObject object="dlt_assets" module="dagster_embedded_elt.dlt" decorator />

In the same file containing your Dagster assets, you can create an instance of your <PyObject object="dlt_assets" module="dagster_embedded_elt.dlt" decorator /> by doing something like the following:

<Note>
If you are using the{" "}
<a href="https://dlthub.com/docs/api_reference/sources/sql_database/__init__#sql_database">
sql_database
</a>{" "}
source, consider setting <code>defer_table_reflect=True</code> to reduce
database reads. By default, the Dagster daemon will refresh definitions
roughly every minute, which will query the database for resource definitions.
</Note>

```python
from dagster import AssetExecutionContext, Definitions
from dagster_embedded_elt.dlt import DagsterDltResource, dlt_assets
Expand Down
Loading