This message was deleted.

The lineage step is likely the step of the BigQuery extraction process that is running into errors, which would cause this bug.

Hey Evan, any ETA on this fix?

Can you try manually running an extraction on your BigQuery integration. We pushed some updates over the weekend and you can test if that resolved the issue

Tried again, but same issue:

Okay let me prioritize this today and make sure it's working for you by tomorrow at the latest. Apologies about the delays

Thank you! much appreciated

Hey Sarin, we've just pushed a change to fix this issue. Please let me know if it's been resolved. Thank you for your patience. If you need your free trial extended please let me know!

Thanks a lot Andrew.! Yes the extraction was successful and I can now see the downstream/upstream details. On another note, what’s the best way to interpret this data?

That's great that it's working now. Here's how you can interpret the data through two examples: If you have two tables table A and B, and B is downstream of A that means that table A was used to make table B through a JOIN for example. And then there is a depth number which means how many JOINs the table is away. Another example with table A, B and C. Where A is used to make B and B is used to make C. If you were on Secoda and looking at table A then B and C would be downstream of A where B has depth 1 and C has depth 2.

Thanks for the example. Say if I’m viewing table A in the catalog, B would appear under downstream right? Please correct if I’m wrong

That's correct Sarin

Ok.. so I feel like details shown is opposite of what you described for the BQ integration I created. We have Table A which which is then used to create B. However B shows as Upstream and not Downstream.

Sorry Sarin, you're correct it is the opposite of how I described it. Even I get it mixed up sometimes 😅 What's the name of your workspace again, so I can extend the trial?

I think it’s Forto

I've extended your free trial by a week Sarin

Thank you Andrew