https://linen.dev logo
Join Slack
Thread
#secoda-support
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    Also, I remember upstream and downstream used to have info a while ago. However, I do not see them for any tables after the recent sync.
    👀 1✅ 1
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    The lineage step is likely the step of the BigQuery extraction process that is running into errors, which would cause this bug.
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    Hey Evan, any ETA on this fix?
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    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
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    Tried again, but same issue:
    Copy to Clipboard
    Neither do I see the, upstream and downstream data for the tables.
    Copy to Clipboard
    This is pretty important for the demo that I want to present internally
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    Okay let me prioritize this today and make sure it's working for you by tomorrow at the latest. Apologies about the delays
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    Thank you! much appreciated
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    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!
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    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?
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    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.
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    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
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    That's correct Sarin
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    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.
    Copy to Clipboard
    Also, please extend the trail period again. Thanks 🙏
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    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?
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    I think it’s Forto
    e

    elegant-house-93198

    1 year ago
    Copy to Clipboard
    I've extended your free trial by a week Sarin
    e

    early-market-3082

    1 year ago
    Copy to Clipboard
    Thank you Andrew
View count: 1
Join thread in Slack