Hi all! We are trying out the `column level lineag...
# troubleshoot
a
Hi all! We are trying out the
column level lineage
functionality of the latest version (
v0.9.0
) and we have an issue with the new lineage visualization there. Context: We are ingesting data from Snowflake, DBT and Looker and we can see a cross-system lineage of the entities involved. Once I enable the "Show Columns" function, I can see all columns appear but I am unable to select any of the columns for most of the tables involved. It seems that column lineage can not be identified for mixed DBT/Snowflake models in this case hence I don't see more column-related edges or can not select/lock any of these columns. Are these kind of mixed models involving DBT supported currently for this feature and what is the plan on DBT side for this? Is there any related configuration that we are not taking into account? (i.e. start-time of lineage?) Also, are there any more detailed docs available about the new column-level lineage functionality? Thanks 🙂
b
hey Giorgos! great questions - first, I believe we only support extracting column-level lineage via ingestion with snowflake as of right now (and you have to be on the most recent version of the CLI if you're using CLI-based ingestion). Second, we have seen some issues if your columns are using the version 2 formatting of their field paths, however we just pushed a fix for that and it is now on
head
and will be out with the next release as well (within the next week or so). Do you know if you're using V2 field paths on your columns?
and yes documentation for column-level lineage visualization as well as the impact analysis (coming in the next release) will be up soon! we're actually working on those presently 🙂