Hi everyone waveboi are there any plans to support

column-level-lineage

functionality when DBT metadata is involved? We are ingesting metadata from Snowflake, DBT and Looker (latest version) and currently it is not possible to use this for merged *Snowflake*&*DBT* entities. It would be really nice to unlock this feature for cases when DBT nodes are part of the lineage (which is probably the most of the cases). Thanks 🙂

I believe this is a bug in our column-level lineage viz. If you’re ingesting column-level lineage from snowflake, we should be showing that in the lineage graph but it seems we’re not doing so cc @bulky-soccer-26729 - as an example, I can see column-lineage here of human_profiles column postal_code -> pet_details here, but I can’t see it when I focus on the human_profiles table here

oh yeah this is definitely a siblings situation thing - the column level lineage must exist here on the non primary sibling so when we compress the lineage we get data from that entity but not the other

Hi @gray-shoe-75895 @bulky-soccer-26729 Thanks for the replies. Are there any updates or an estimation on when would this be available?

hey Girogos! I appreciate the reminder, so sorry we've been slow on this update - it's just been busy with other feature dev and holidays and what not. I can't specifically say an ETA but I can say I'm going to move the ticket I created for this up in priority to officially get slotted for work! I'd say we can tackle it potentially before our next release, but most likely the release after that. Thanks again for the reminder here!