![]() After a successful beta period, we will announce the deprecation of the single-file definition option. The new batch definition option is in beta. You no longer have to define every asset used in lineage relation in a separate section. Support for any asset type with stitching. ![]() Support for indirect and table-level lineage as well as column-level lineage. When creating a custom technical lineage, you can now opt for the new batch definition option, which includes the following benefits:.Previously, you might experience HTTP 401 Unauthorized errors due to too many concurrent requests. When you create technical lineage for Looker, you can now define the number of concurrent request and connection timeout in the configuration file.You can create technical lineage for dbt Cloud and dbt Core by using the lineage harvester and technical lineage via Edge. Collibra Data Lineage support for dbt Cloud and dbt Core is now generally available.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |