-
Notifications
You must be signed in to change notification settings - Fork 186
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.
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/issue 1661 add tip to source docs and update weaviate docs #1662
Conversation
✅ Deploy Preview for dlt-hub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, added some comments :)
@@ -116,6 +116,22 @@ weaviate_adapter( | |||
tokenization={"title": "word", "description": "whitespace"}, | |||
) | |||
``` | |||
When adapting resources, it's important to implement changes directly to the data source itself rather than extracting resources separately. Here's how: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When adapting resources, it's important to implement changes directly to the data source itself rather than extracting resources separately. Here's how: | |
When using the `weaviate_adapter`, it's important to apply it directly to resources, not to the whole source. Here's an example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
destination="weaviate", | ||
) | ||
|
||
# adapt the resource within the source |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# adapt the resource within the source | |
# apply adapter to the needed resources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
:::tip TIP | ||
The `max_table_nesting` parameter at the source level doesn't automatically apply to individual | ||
resources when accessed directly (e.g., using `source.resources["resource_1"])`. To make sure it | ||
works, either use `source.with_resources("resource_1")` or set the parameter directly on the resource. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please, add an example how parameter could be set directly in the resource
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Also, please add the same info about adapter for qdrant https://deploy-preview-1662--dlt-hub-docs.netlify.app/docs/dlt-ecosystem/destinations/qdrant/#qdrant_adapter and lancedb https://deploy-preview-1662--dlt-hub-docs.netlify.app/docs/dlt-ecosystem/destinations/lancedb/#run-the-pipeline |
products_tables = sql_database().with_resources("products", "customers") | ||
|
||
pipeline = dlt.pipeline( | ||
pipeline_name="postgres_to_weaviate_pipeline", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pipeline_name="postgres_to_weaviate_pipeline", | |
pipeline_name="postgres_to_lancedb_pipeline", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
|
||
pipeline = dlt.pipeline( | ||
pipeline_name="postgres_to_weaviate_pipeline", | ||
destination="weaviate", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
destination="weaviate", | |
destination="lancedb", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
products_tables = sql_database().with_resources("products", "customers") | ||
|
||
pipeline = dlt.pipeline( | ||
pipeline_name="postgres_to_weaviate_pipeline", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pipeline_name="postgres_to_weaviate_pipeline", | |
pipeline_name="postgres_to_qdrant_pipeline", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
|
||
pipeline = dlt.pipeline( | ||
pipeline_name="postgres_to_weaviate_pipeline", | ||
destination="weaviate", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
destination="weaviate", | |
destination="qdrant", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
... | ||
``` | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or | |
```py | |
my_source = my_source() | |
my_source.my_resource.max_table_nesting = 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Description
#1661
This PR clarifies the behavior of the
max_table_nesting
parameter, ensuring users understand that it doesn’t automatically apply to individual resources. It provides guidance on how to correctly apply the parameter to achieve the desired effect.